User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 GTB6 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 Performed the upgrade, now the client will not send mail. No settings have changed (my user name, password or sending through port 587), but error message was it could not send mail. I did go in and mess with various settings and found, if you turned off 'use secure authentication' (found in account settings | outgoing server (smtp), then select edit for the outgoing juno account, and the setting box for this will appear) the mail will send. So, mail is now working, but you may have others that - after upgrading to the most recent client, need to update their settings as listed above. Reproducible: Always

(In reply to comment #0) > So, mail is now working, but you may have others that - after upgrading to the > most recent client, need to update their settings as listed above. > Thanks for the report ! We don't have a complete fix yet.

It is somewhat disturbing that these issues still occur despite a mitigating patch having been checked in for bug 522633 in time for the 3.0 release. Bryan, could you provide some more information by executing the following from a command line to probe for the capabilities of your provider's server: > Enter on command prompt: $ telnet my.server.com 25 > Response from server: 220 my.server.com ESMTP ready (or similar) > Enter greeting: EHLO just.testing.com > Multi-line response: 250-... > Close connection: QUIT > Response from server: 221 Bye! > Connection closed by foreign host. and copy-paste the "250-" response lines into a comment posted here? This may help to narrow down which secure-authentication cases aren't covered yet.

Uising Vista Ultimate (SP2) on this client. Opening a command prompt and typing in the commands as given produced a command not recognized. Downloaded puttytel and ran using this command authsmtp.juno.com 587 Below is the response. 220 smtpout01.vgs.untd.com ESMTP EHLO just.testing.com 500 Command unrecognized Probably not too much help, but settings above could assist for smtp and port.

Interesting (command is correct), trying the same I got the following response: > 250-smtpout05.vgs.untd.com Hello ... please to meet you > 250-SIZE > 250-8BITMIME > 250-AUTH LOGIN PLAIN CRAM-MD5 > 250 HELP Thus, the CRAM-MD5 response apparently prompted the "secure suthentication" setting to be switched on during migration, but it apparently didn't work. That's more like bug 539944 in this case, but the underlying issue may be the same as bug 522633. Thanks for testing.