Forum Discussion
What's your Timeout setting? Perhaps you could try increasing it.
Bruce, thanks for the suggestion. Obviously I don't believe that this is something that users should have to tinker with because of ill-advised changes made by TPTB, but what the heck. I went in and doubled the default timeout from 100 to 200 and re-started T-bird. No joy, same error. I then increased it to 500 with another re-start; same result. I get the distinct impression that the lights are on but nobody's home at the SMTP server ...
- sw231855 years agoNew Contributor III
Still no solution, 15 days and counting ...
- sw231855 years agoNew Contributor III
Still no solution, 18 days and counting ...
- sw231855 years agoNew Contributor III
Just called in to Cox Support again (sixth try is a charm) and got hold of a Tier 2 specialist named Chris that actually knew what he was talking about, was polite, and communicated clearly.
He reviewed the notes for my support ticket and then unexpectedly told me to switch *back* to the original port 465 instead of the 'new' 587 communicated by other agents. After forcing my Thunderbird to recognize the new setting I am now able to send and receive successfully from both my laptop and iPhone (via Mail).
A big thank you' to Chris, although the reality is that this problem never should have happened in the first place, much less taken more than two weeks to resolve!!!
Related Content
- 5 years agoMzzmel
- 4 months agoJESinFC
- 11 years agoModem_upstream_