Closed Bug 529502 Opened 10 years ago Closed 8 years ago

GMX SMTP server "use secure authentication" is enabled by default

Categories

(Thunderbird :: Account Manager, defect)

x86
Windows Vista
defect
Not set

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: emoore, Unassigned)

References

Details

(Keywords: regression, Whiteboard: [closeme 2012-01-11])

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.5) Gecko/20091117 Thunderbird/3.0

I'm sharing a profile between Thunderbird 2.0.0.23, Shredder beta 4, the 11/13 Shredder nightly build and build 2 of 3.0 RC1. One of my IMAP accounts is for GMX. It uses a SSL connection via port 993 to imap.gmx.com and no secure authentication. Its SMTP server is set to mail.gmx.com using port 587 and "TLS if available". "Use name and password" is checked.

I can send messages from it with every version except build 2 of 3.0RC1. It complains that:

Sending of message failed.
An error occurred sending mail: Unable to authenticate to SMTP server mail.gmx.com. The server does not support any compatible secure authentication mechanism but you have chosen secure authentication. Try switching off secure authentication or contact your service provider.

This build added a "use secure authentication" setting to the SMTP server entry and enabled it by default. 

After unchecking "use secure authentication" I could send messages. I checked the other SMTP server entries (Fastmail, Gmail, Google Apps, AIM, Hotmail, webmail/localhost) and none of them had "use secure authentication" enabled by default.






Reproducible: Always
Blocks: qa-tb3.0rc1
regression?
Keywords: regression
Version: unspecified → 3.0
(In reply to comment #1)
> regression?

Probably a dupe of one of David's bugs.
Sounds like bug 522633, but with the added twist of sharing a profile. That
SMTP server gives me an AUTH LOGIN PLAIN, thus should fail on trySecAuth and
fall back to plain authentication. Maybe that preference is somehow changed
when used with a 2.0 profile, but then it should be the same problem with the nightly builds.

Can you identify the server and provide the mail.smtpserver.smtp#.trySecAuth
and mail.smtpserver.smtp#.useSecAuth preference values?

If you reset both to force a retry, does it come up with the box checked again on the next message you try to send?
Eric, can you retest per comment 3 please?
Whiteboard: [closeme 2012-01-11]
RESOLVED INCOMPLETE due to lack of response to previous question. If you feel this change has been made in error, please respond to this bug with your reason why.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.