Thunderbird 102, SMTP and GMAIL
Thunderbird can receive emails correctly (imap) but is unable to send (smtp). Recent problem, no changes to configuration.
Thunderbird 102.2.2 (64-bit) Linux Mint 20 IMAP server config:
imap.gmail.com:993 t****.f****@gmail.com ssl/tls OAuth2
SMTP server config
smtp.gmail.com:465 t****.f****@gmail.com ssl/tls OAuth2
Recent problem, no changes to configuration. Only affects GMAIL (Yahoo works OK). Have deleted and reinstalled TB Have deleted and reinstalled all mail accounts and pw Have cleared DNS cache and treid smtp.googlemail.com (same problem so reset)
Developer error console has following messages immediately aafter an attempted email send:
mailnews.smtp: error { target: TCPSocket, isTrusted: true, name: "ConnectionRefusedError", message: "Network", errorCode: 2152398861, srcElement: TCPSocket, currentTarget: TCPSocket, eventPhase: 2, bubbles: false, cancelable: false, … } bubbles: false cancelBubble: false cancelable: false composed: false composedTarget: TCPSocket { host: "smtp.gmail.com", port: 465, ssl: true, … } currentTarget: null defaultPrevented: false defaultPreventedByChrome: false defaultPreventedByContent: false errorCode: 2152398861 eventPhase: 0 explicitOriginalTarget: TCPSocket { host: "smtp.gmail.com", port: 465, ssl: true, … } isReplyEventFromRemoteContent: false isSynthesized: false isTrusted: true isWaitingReplyFromRemoteContent: false message: "Network" multipleActionsPrevented: false name: "ConnectionRefusedError" originalTarget: TCPSocket { host: "smtp.gmail.com", port: 465, ssl: true, … } returnValue: true srcElement: TCPSocket { host: "smtp.gmail.com", port: 465, ssl: true, … } target: TCPSocket { host: "smtp.gmail.com", port: 465, ssl: true, … } timeStamp: 0 type: "error" <get isTrusted()>: function isTrusted() <prototype>: TCPSocketErrorEventPrototype { name: Getter, message: Getter, errorCode: Getter, … } SmtpClient.jsm:433:17
_onError resource:///modules/SmtpClient.jsm:433
mailnews.send: Sending failed; The message could not be sent because connecting to Outgoing server (SMTP) smtp.gmail.com failed. The server may be unavailable or is refusing SMTP connections. Please verify that your Outgoing server (SMTP) settings are correct and try again., exitCode=2153066798, originalMsgURI= MessageSend.jsm:335:27
fail resource:///modules/MessageSend.jsm:335 _deliveryExitProcessing resource:///modules/MessageSend.jsm:631 sendDeliveryCallback resource:///modules/MessageSend.jsm:685 OnStopRunningUrl resource:///modules/MessageSend.jsm:1313 onerror resource:///modules/SmtpService.jsm:188 _onError resource:///modules/SmtpClient.jsm:447
Ideas most welcome.
所有回复 (3)
Whoa ... Mozilla what are you doing.
So it works and here's what I changed. I went to my SMTP settings ... now for Yahoo.com and Seznam.cz the SMTP profile description is left "blank". For Gmail it is set to "GMail".
So for each account (5 gmail addresses) I entered a unique description name. Thinks, at the time, no idiot would select the smtp profile from the description name ... would they?
Restarted TB and, what would you know, suddenly I can send email! Tell me, surely, TB does not use the description name to identify the SMTP profile to use ... surely not. But then changing the descriptions to a unique name for each account would imply TB is doing just that.
As a retired IT dinosaur I'm shocked and must add: "Name, description, "whatever text" is NOT a robust identification method. Must do better!"
No, I take that all back and offer apologies. I restarted TB and it went back to NOT sending emails! This app has problems!
For completeness here's the pop up msg:
Sending of the message failed. The message could not be sent because connecting to Outgoing server (SMTP) smtp.gmail.com failed. The server may be unavailable or is refusing SMTP connections. Please verify that your Outgoing server (SMTP) settings are correct and try again.
Checked all the settings ... again! and they are correct, as far as I can see. I do wonder why it worked for 2 messages then stopped again.
This question has been locked because the original author has deleted their account. While you can no longer post new replies, the existing content remains available for reference.