Forum Discussion
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.
- Becky6 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- HGW6 years agoNew Contributor
Hello, Becky. Avast completely disabled and was able to send one message. Then got same blocking message from Cox. What now?
- MarkM16 years agoFormer ModeratorHGW,
I would like to have you try a different outgoing mail setting. Would you change the security type to TLS & use port 587? Please let us know if this works for you.
Mark M.
Cox Support Forums Moderator
- HGW6 years agoNew Contributor
Hi, Becky, Avast was disabled and could send one test message, after that blocked again with same message from Cox. What now?