X
Tippen Sie hierhin, um die Version dieser Website für Mobilgeräte aufzurufen.

Hilfeforum

Unable to send emails. Error message says SMTP server timeout

Veröffentlicht

Yesterday afternoon at approx 3:30 pm (July 22 2017) I successfully sent four (4) emails. I tried to send more at approx 5 pm, received message"

Sending of the message failed. The message could not be sent because the connection to Outgoing server (SMTP) smtp.cox.net timed out. Try again.

I have spoken with my ISP (Cox Communications, Phoenix), they say my account is fine. It is active, I am not blocked from sending emails. Further, I successfully signed in to their online email service, and was able to send emails without error.

Cox says the problem is with my email software, or a setting. Settings were changed to day per Cox recommendations (July 23 2017). That I can identify, nothing changed on my PC yesterday.

Running Windows 10, 64 bit, all maintenance is current.

Yesterday afternoon at approx 3:30 pm (July 22 2017) I successfully sent four (4) emails. I tried to send more at approx 5 pm, received message" Sending of the message failed. The message could not be sent because the connection to Outgoing server (SMTP) smtp.cox.net timed out. Try again. I have spoken with my ISP (Cox Communications, Phoenix), they say my account is fine. It is active, I am not blocked from sending emails. Further, I successfully signed in to their online email service, and was able to send emails without error. Cox says the problem is with my email software, or a setting. Settings were changed to day per Cox recommendations (July 23 2017). That I can identify, nothing changed on my PC yesterday. Running Windows 10, 64 bit, all maintenance is current.

Ausgewählte Lösung

Cox says you should use smtp.cox.net on port 587 with STARTTLS security or port 465 with SSL/TLS security, authentication = normal password and User name = part of your address before the @. Sending on smtp is different from sending through webmail, so success with the latter does not ensure success with the former.

What are your settings, and did you change your password?

Diese Antwort im Kontext lesen 4

Mehr Details zum System

Anwendung

  • User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Weitere Informationen

sfhowes
  • Top 10 Contributor
1816 Lösungen 8948 Antworten
Veröffentlicht

Ausgewählte Lösung

Cox says you should use smtp.cox.net on port 587 with STARTTLS security or port 465 with SSL/TLS security, authentication = normal password and User name = part of your address before the @. Sending on smtp is different from sending through webmail, so success with the latter does not ensure success with the former.

What are your settings, and did you change your password?

[https://www.cox.com/residential/support/imap-server-settings.html Cox says] you should use smtp.cox.net on port 587 with STARTTLS security or port 465 with SSL/TLS security, authentication = normal password and User name = part of your address before the @. Sending on smtp is different from sending through webmail, so success with the latter does not ensure success with the former. What are your settings, and did you change your password?
Veröffentlicht

Fragesteller

Hi sfhowes Thanks for taking the time to reply, much appreciated.

All my settings are as you described. 465 with SSL/TLS, and, normal password, and username as the first part of each email address. I changed my password as a last attempt to fix this last night, thinking perhaps it had expired (though receiving emails is working fine). All to no avail.

COX is essentially saying "sending by webmail works fine, so the problem is not at our end". As far as I can tell, nothing changed at my end. No Windows updates Saturday afternoon, T'bird itself was updated back in June. What still makes me suspect COX is they "upgraded" my email service last week, which is usually doublespeak for "we wanted to get rid of something at our end".

I use these email addresses for a business that I run, and saving my "sent" emails is important to me. Using Webmail won't cut it, and I really don't want to use Outlook.

Re-reading your info - COX told me to use SSL/TLS security with either port. Both tried, both failed. I had not tried the STARTTLS with 587 combination - THAT WORKED !!!

Thanks VERY much !!!

Hi sfhowes Thanks for taking the time to reply, much appreciated. All my settings are as you described. 465 with SSL/TLS, and, normal password, and username as the first part of each email address. I changed my password as a last attempt to fix this last night, thinking perhaps it had expired (though receiving emails is working fine). All to no avail. COX is essentially saying "sending by webmail works fine, so the problem is not at our end". As far as I can tell, nothing changed at my end. No Windows updates Saturday afternoon, T'bird itself was updated back in June. What still makes me suspect COX is they "upgraded" my email service last week, which is usually doublespeak for "we wanted to get rid of something at our end". I use these email addresses for a business that I run, and saving my "sent" emails is important to me. Using Webmail won't cut it, and I really don't want to use Outlook. Re-reading your info - COX told me to use SSL/TLS security with either port. Both tried, both failed. I had not tried the STARTTLS with 587 combination - THAT WORKED !!! Thanks VERY much !!!
Bob Rudolph 0 Lösungen 1 Antworten
Veröffentlicht

Hilfreiche Antwort

For any .NET developers coming across this, it seems that Cox is forcing all email access to SSL starting on 25 Jan 2018. For programmatically sending emails, the following code worked for me:

Dim lSmtpClient = New SmtpClient("smtp.cox.net") lSmtpClient.Credentials = New System.Net.NetworkCredential("AccountUserNameBeforeThe@", "AccountPassword") lSmtpClient.Port = 587 lSmtpClient.EnableSsl = True

For any .NET developers coming across this, it seems that Cox is forcing all email access to SSL starting on 25 Jan 2018. For programmatically sending emails, the following code worked for me: Dim lSmtpClient = New SmtpClient("smtp.cox.net") lSmtpClient.Credentials = New System.Net.NetworkCredential("AccountUserNameBeforeThe@", "AccountPassword") lSmtpClient.Port = 587 lSmtpClient.EnableSsl = True
DcnDon 1 Lösungen 5 Antworten
Veröffentlicht

Hilfreiche Antwort

I have this problem as well. Cox supposedly filed an incident and was supposed to get back to me within 48 hours - 3 days and still no response!

I tried the STARTTLS with 587 port as noted sfhowes reply above, but that DID NOT work for me. I have NO problems sending emails with the new Cox configuration, but can't send emails! I do not get the server timeout, but a login failure. I have reset the password to no avail. I have closed and restarted Tbird each time trying something new. Like sfhowes, the Web interface does not work well for me.

I'd appreciate some help. Thanks!

I have this problem as well. Cox supposedly filed an incident and was supposed to get back to me within 48 hours - 3 days and still no response! I tried the STARTTLS with 587 port as noted sfhowes reply above, but that DID NOT work for me. I have NO problems sending emails with the new Cox configuration, but can't send emails! I do not get the server timeout, but a login failure. I have reset the password to no avail. I have closed and restarted Tbird each time trying something new. Like sfhowes, the Web interface does not work well for me. I'd appreciate some help. Thanks!
sfhowes
  • Top 10 Contributor
1816 Lösungen 8948 Antworten
Veröffentlicht

DcnDon said

I have this problem as well. Cox supposedly filed an incident and was supposed to get back to me within 48 hours - 3 days and still no response! I tried the STARTTLS with 587 port as noted sfhowes reply above, but that DID NOT work for me. I have NO problems sending emails with the new Cox configuration, but can't send emails! I do not get the server timeout, but a login failure. I have reset the password to no avail. I have closed and restarted Tbird each time trying something new. Like sfhowes, the Web interface does not work well for me. I'd appreciate some help. Thanks!

Start Windows in safe mode and see if you can send mail. If it works, it means there is a security program interfering with the secure connection. See this post for an example:

https://support.mozilla.org/en-US/questions/1199185

''DcnDon [[#answer-1064358|said]]'' <blockquote> I have this problem as well. Cox supposedly filed an incident and was supposed to get back to me within 48 hours - 3 days and still no response! I tried the STARTTLS with 587 port as noted sfhowes reply above, but that DID NOT work for me. I have NO problems sending emails with the new Cox configuration, but can't send emails! I do not get the server timeout, but a login failure. I have reset the password to no avail. I have closed and restarted Tbird each time trying something new. Like sfhowes, the Web interface does not work well for me. I'd appreciate some help. Thanks! </blockquote> Start Windows in safe mode and see if you can send mail. If it works, it means there is a security program interfering with the secure connection. See this post for an example: https://support.mozilla.org/en-US/questions/1199185
DcnDon 1 Lösungen 5 Antworten
Veröffentlicht

Thanks, I did as you suggested and started Windows in safe mode. The results are the same. I cannot send email and the error message remains. It appears that there is a problem with the login password, but it is exactly the same as the one used to retrieve email and that works fine.

Thanks, I did as you suggested and started Windows in safe mode. The results are the same. I cannot send email and the error message remains. It appears that there is a problem with the login password, but it is exactly the same as the one used to retrieve email and that works fine.