1272177 - {imap.smtp}.aim.com suddenly requires "connection security" to be "none" instead of STARTTLS which I have used for years.

Status: RESOLVED INVALID

(SeaMonkey :: MailNews: Account Configuration, defect)

Description

[muddflapp mohican]

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40
Build ID: 20160120202951

Steps to reproduce:

Several years ago I configured seamonkey mail to stop using pop and use IMAP.
I took it to the highest security that the servers would let me which was:
imap.aim.com port 143 Connection Security: STARTTLS, authentication "Normal Passw"
smtp.aim.com port 587 Connection Security: STARTTLS, authentication "Normal Passw"


Actual results:

5/11/2016: 
Tries to connect, never asks for a password, doesn't complain, stops trying.
I had to change Connection Security to "none" and Authentication method: "Password, transmitted insecurely". Then it asks for password and does it's job.



Expected results:

Reverted back to Seamonkey 2.39, same problem, went back to 2.40
Is this an imap.aim.com, smtp.aim.com reconfiguration that happened at their end?

Comment 1

[Rainer Bielefeld]

Because user has the problem with 2.39 and 2.40 this is not a SM 2.40 problem. Sounds like a problem with the email service provider, not like a SeaMonkey problem, here <http://allestörungen.de/stoerung/aol> I read about AIM email problems starting 2016-05-10.

@Reporter: Please feel free to reopen this Bug if you can contribute some plausible reasons why this might be a SeaMonkey problem ("Works fine with Thunderbird and ...") with some results of your discussion with AOL support, AIM user forum or something similar.
If you find hints that your problem is a SeaMonkey problem you should try in safe mode with disabled add-ons and also with a newly created user profile.

Comment 2

[muddflapp mohican]

Naturally it was something I had done and forgot about it.
I went to Privacy and Security --> SSL/TLS and turned off TLS 1.0 and TLS 1.1 and left only TLS 2.0
I turned on TLS 1.0 and it started working again.

Comment 3

[Rainer Bielefeld]

(In reply to muddflapp mohican from comment #2)
Thank you for your feedback.