On 02/16/16 12:56 PM, Jonathan N. Little wrote:
Keith Thompson wrote:
<snip>
Yes, have tried both. I will comment that I had removed all passwords
from the password manager and when signing in to retrieve my mail,
entered my standard password for the pop. It accepted it and retrieved
the mail just fine. It is apparent now, that there is something
affecting the smtp connection. Normally, this would be the port, but I
have tried the old 25, the new 587 and another that I ran across in one
of the blogs. It was in the 400's, but I don't recall the exact value.
It didn't work either.
Well reference this might give a clue as to where to focus on to debug this.
<http://www.serversmtp.com/en/smtp-error>
How as another possibility just encountered with a friend where Gmail suddenly
stopped accepting their username/password on their account. I guess Google is
trying to get everyone to use Chrome because what I had to do was in their
account settings was to enable "less secure applications" to use Thunderbird
or SeaMonkey. Maybe WOW has something similar?
Actually, WOW has increased their security. Until recently, I only had to
sign in on the POP retrieval and no security on sending. The change is what
has caused me the problems. I am investigating the router which may be
responding with the wrong port (25) and blocking my setting of 587. More later.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
