MCBastos wrote:
This is a known issue. In the old Seamonkey, if you chose to use
authentication or encryption in your POP/SMTP connections and the server
didn't support it, Seamonkey silently fell back to
unencrypted/unauthenticated mode and did the connection anyway.
The new Seamonkey 2 doesn't do that -- if you ask for higher security
and the server doesn't provide it, it simply doesn't connect.
Actually, I believe this is probably something else, as that specific
"problem" should have been fixed in 2.0.3 by going back to not doing the
additional check.
Robert Kaiser
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
