Closed Bug 1544827 Opened 7 years ago Closed 7 years ago

Slow or no response with Cox Mail Servers

Categories

(MailNews Core :: Networking: SMTP, defect)

Product:
MailNews Core
Component:
Networking: SMTP
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: n1api, Unassigned)

References

(
URL
)

Details

(Whiteboard: [support])

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0

Steps to reproduce:

Called Cox

Actual results:

Thunderbird has been slow to both sign on, retrieve and send mail to the Cox email servers. Today it stop working completely. I called Cox who said that I should notify Mozilla. They do not know why it is so slow or unresponsive to their mail servers.

Expected results:

Should work with the COX mail servers. Also should be faster.

Component: Untriaged → Networking: SMTP
OS: Unspecified → Windows 7
Product: Thunderbird → MailNews Core
Hardware: Unspecified → x86
Whiteboard: [support]

https://www.cox.com/residential/support/imap-server-settings.html

Note from the page
As of April 23, 2019, SSL will no longer be a valid security setting. All customers with SSL enabled will need to disable SSL or will no longer be able to send or receive email.

I am not sure what Cox customers are supposed to do for connection encryption after that date. However I would guess they have jumped their own gun on the SSL thing. Try changing it to none in account settings..

It would appear from the linked support topic that the cox server has port 443 blocked so Thunderbird is not getting certificates. I am sure this is a dup of a core bug 966689

However if we have major ISP's blocking ports, I think this might be more important than it has been in the past. Thoughts Magnus?

URL: https://support.mozilla.org/en-US/que...
Flags: needinfo?(mkmelin+mozilla)

I can't even get past the re-CAPTCHA to read that page.

But, not sure what we could even do about this. I assume thunderbird would start to display a "connnection failed" prompt. What they should do? Complain to cox and have them enable some secure method of connecting again. Or accept that their connection is very insecure and change the settings to whatever is the new recommendation.

Flags: needinfo?(mkmelin+mozilla)

I have been having slow response (over 2 minutes) sending mail from my Comcast account lately and see this error in the console.

NS_ERROR_FAILURE: Couldn't decrypt string crypto-SDR.js:179

The mail does eventually get sent.

Nothing we can do here, see comment #3.

Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.