On 3/4/2010 1:03 PM, Bill Davidsen wrote: > Mark Hansen wrote: >> On 3/2/2010 6:02 AM, Robert Kaiser wrote: >>> 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 >> >> I thought the issue was that after migrating to 2.X, there was an >> option selected for the mail server that shouldn't have been, and >> it needed to be unchecked. >> >> I just can't remember which option it was, but it was one of the >> security/authentication options. >> > Are you thinking of the problem that occurred with news servers which allow > access w/o auth, but post requires auth? If you tried to post you would get > back > a message that your SMTP server had a configuration error. Fixed in 2.0.2. >
No, I was thinking of the issue with the SMTP server settings. However, as Robert has said, this is no longer a problem. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
