Forum Discussion
Incoming Server Settings:
• If you use POP, use pop.cox.net and port 995
• If you use IMAP, use imap.cox.net and port 993
• Use password authentication
• Make sure SSL is enabled
Outgoing Server Settings:
• Server: smtp.cox.net
• Use port number 465
• Make sure SSL is enabled
Some customers have reported they've been unable to use the Secure Password Authentication (SPA) option in Outlook's Advanced Outgoing Settings. You might try disabling Secure Password Authentication (SPA) in Outlook's Advanced Outgoing Settings. Delete any emails stuck in the Outbox, then close and restart your email utility and see if you are able to send a test message successfully. I've also heard from folks who reported they are unable to use the option “Use the same settings as my incoming mail server” in the Outgoing Server settings. You might try changing this setting to the “Log on using” option. Type in your Cox Username (everything before the “@” symbol in your email address) and your Cox password. Then click OK/Apply. Delete any emails stuck in the Outbox, then close and restart your email utility and see if you are able to send a test message successfully. If you have multiple accounts set up in Outlook, be sure to check the server settings for each account. -Becky, Cox Support Forums Moderator
Hello, Becky, thank you for the additional information. Changes showed fine in Outlook and in Microsoft test message, then allowed me to send one test message from my Outlook, then next message bounced back with same error message that Cox thought it was spam. Very frustrating and seems to be a problem on the Cox side. Can Cox clear my individual and default email addresses as "thisisnotspam" and, if so, who do I contact and how? Have previously tried and am unable to reach Cox by telephone or live chat on Internet questions. Thank you.
- Becky7 years agoModeratorHi HGW, are you able to log into Cox Webmail and send mail successfully? -Becky, Cox Support Forums Moderator
- HGW7 years agoNew Contributor
Yes and good point, Becky, I have sent two test emails directly from Cox Webmail and both came through fine. What then could be the trigger for the Cox message blocking sending through Outlook? I am puzzled because after making the changes previously mentioned I was able to send test email once or twice from Outlook, then further emails were blocked again. This happened on both the main Cox account and also the subsidiary email account (which is used on a different computer but also through Outlook). Assuming that I hopefully followed all of your suggestions correctly, what could be the cause of Cox blocking them? Any other suggestions? Thank you.
- Becky7 years agoModeratorHi HGW, some security software can interact with Outlook in weird ways. I found the following regarding Avast (support.avast.com/.../
"If you use an email client (such as Outlook or Mozilla Thunderbird), Avast may include an email signature at the bottom of your outgoing emails to let your recipients know that the email has been scanned for malware. This setting is enabled by default."
Disable the Avast email signature for outgoing emails and try sending a few more test messages. If you still get the 552 5.2.0 error message, disable Avast completely (just in case we're overlooking another Avast setting or tool that is impacting Outlook) and try again. Please let us know what happens! -Becky, Cox Support Forums Moderator
Related Content
- 12 months ago
- 5 years ago
- 7 years ago
- 10 months ago