This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Cannot send emails due to encryption method

I am one of the many Cox customers who cannot send emails from Microsoft Outlook.  I use Outlook 2007.  I have read the numerous postings on this subject.  I have tried ever permutation of outgoing server (smtp) port: 465, 587, & 25 and SSL encryption.  The closest that I get to not getting the error msg "..555 eastrmimpo cox connection refused from 68.83.12" is with port 587.  With 587 and SSL, I get "... Try changing the method of encryption....".  I have spoken and chatted with technical support with no success.

Also, I have checked off my outgoing server (SMTP) requires authentication as well as my username and password.

I receive emails with no issues (at least for now:-))

Does anyone have any suggestions? 

 

  • this is the first time I have heard of this.  I don't think it's millions maybe just you.

    I just sent a test email and it went out.  what email server are you using?

    http://ww2.cox.com/residential/support/internet/article.cox?articleId={a8fb24c0-6440-11df-ccef-000000000000}

  • I want to thank everyone who responded to my post.  I was resolved this problem this evening with help from Cox technical support.  I will summarize what fixed my problem for others.

    First, I use a different Internet Service Provider (ISP) provider than Cox.  Therefore, I was told that I had to use the SMTP mail server of my current ISP provider not Cox to send emails.  This was the root cause issue.  I changed the outgoing mail server to my current ISP in Microsoft Outlook . Now, I can send emails again with no issues.  It was a 5 min solution in the hands of a very capable technical support staff member.

    In summary,  you have to change

    "smtp.cox.net" to "smtp.your ISP's name.net"

    In the Advanced Tab, I had to input in my ISP server# in the "Outgoing server (SMTP):" box,. You have to follow the instructions from your current ISP in order to set up Microsoft Outlook or any other email client properly. Mine was on their website.

    For incoming mail, I continue to use the Cox incoming mail server ("pop.cox.net") in order to access my email.  That's why I was continuing to receive emails with no issues.  I made a suggestion to Cox to create a technical bulletin with instructions on how to handle my situation.  These instructions would be helpful to Cox customers.  We live in a very mobile society so it is not unusual for users to change their ISP provider due to a variety of reasons. 

     I apologize in advance for my explanation. I'm not a computer techie so this is my attempt to convey general information only.  Hopefully, it points someone with similar issues in the right direction.

    In closing, my key learning was that my outgoing mail server (SMTP) must match my Internet Service Provider's outgoing mail server. 

     

     

  • "In closing, my key learning was that my outgoing mail server (SMTP) must match my Internet Service Provider's outgoing mail server. "

    That isn't quite accurate. The instructions that Chris gave are correct but where people get stuck are in the details. The issue is Cox blocks inbound port 25 into their network. This is a common security measures most ISP take to cut down on spammers.  So with port 25 out, you have to use 465 or 587. Both of those ports require username and passwords, to make sure you have a Cox account, and encryption, to protect (somewhat) the information your sending. Where they differ is the type of encryption. 465 forces SSL while 587 works with SSL and TLS. Where it gets tricky is TLS implantation, but thats kind of beyond scope, but basically sometimes you just have to try both and see which one works with your particular client (Outlook, Thunderbird, Mac Mail, etc) and what network your sending from (Verizon, ATT, Comcast, etc). Also, some local networks (IE your router/firewall) will block those ports, or your Antivirus will scan your outbound email and delay it long enough for the SSL connection to time out. I suspect that may have been what happened to you, and thats why you had to use port 25, which meant using the SMTP server of the ISP your on.

    So in short, I don't deny your results, you isolated the issue and found a work around. However, in general, using smtp.cox.net with username/password on outbound with SSL on port 465 will work outside of the Cox network. I personally use it on my Android phone while on Sprint, and a desktop using Outlook on Comcast. Result will vary, but just wanted to give some insight in-case anyone stumbled upon this thread.