stopped sending messages when updated to 45.1.0
Hi,
outgoing emails were working until the 45.1.0 update that was applied today. Now thunderbird refuses to send email. "The message could not be sent using Outgoing server (SMTP) "my server's name" for an unknown reason. Please verify that your Outgoing server (SMTP) settings are correct and try again."
"my server's name" is actually my server's name (not "my server's name" literally.
I am not running third party virus scanners or firewalls. I am a computer scientist. I have my own SMTP server connected to a university network. (the server still works on all my other computers and devices, including an almost verbatim copy of my laptop that was not yet updated to 45.1.0).
Looking at the mailserver's log (as I have access to it):
May 16 22:18:08 XXXXX sendmail[25636]: STARTTLS=server, error: accept failed=-1, SSL_error=1, errno=0, retry=-1, relay=XXX [XXX]
May 16 22:18:08 XXXXX sendmail[25636]: STARTTLS=server: 25636:error:1408A0C1:SSL routines:SSL3_GET_CLIENT_HELLO:no shared cipher:s3_srvr.c:1352:
May 16 22:18:08 XXXXX sendmail[25636]: u4H3I84G025636: XXX [XXX] did not issue MAIL/EXPN/VRFY/ETRN during connection to TLSMTA
it seems that thunderbird has dropped some ciphers that were used previously. Or is this a cert related issue? Was cert acceptance modified? Could you please confirm any of these?
(this is what I see when sending through another laptop with the old thunderbird:
May 16 22:20:21 XXXXX sendmail[25672]: STARTTLS=server, relay=XXX [XXX], version=TLSv1/SSLv3, verify=NO, cipher=RC4-SHA, bits=128/128
May 16 22:20:21 XXXXX sendmail[25672]: AUTH=server, relay=XXX [XXX], authid=XXX, mech=PLAIN, bits=0
May 16 22:20:22 XXXXX sendmail[25672]: u4H3KL2m025672: from=<XXX>, size=365, class=0, nrcpts=1, msgid=<XXX>, proto=ESMTP, daemon=TLSMTA, relay=XXX [XXX]
May 16 22:20:22 XXXXX sendmail[25677]: STARTTLS=client, relay=XXX, version=TLSv1/SSLv3, verify=OK, cipher=CAMELLIA256-SHA, bits=256/256
May 16 22:20:22 XXXXX sendmail[25677]: u4H3KL2m025672: to=<XXX>, delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=120365, relay=XXX [XXX], dsn=2.0.0, stat=Sent (ok: Message 316365732 accepted)
)
由 GregZ 於 修改
所有回覆 (2)
Seeing the sslv3 and rc4 ciphers in the old version that still works I'm gonna say contact your cert owner / maintainer as not only has it now prevented you form using Thunderbird through it, MOST browsers are making the same moves FF 46 and chrome 48 made the same changes (fixing that cert now will alleviate way more issues in the coming months for ALL users on that SMTP server)..
It was a cipher issue; Thunderbird changed something on how ciphers were negotiated. Did some changes on the mail server cipher settings and it works again.