91 killed sending email
Thunderbird automatically updated last night and now I can't send email from any of my accounts. All incoming works just fine. Unlike some of the others I've read, my address book seems just fine. The only problem is that the server is rejecting all of my email accounts now. I have made zero changes. I have since tried working with the tech support for Shaw and they're stumped and referred me here.
Here's the error message with my email addy removed: Sending of the message failed. An error occurred while sending mail. The mail server responded: <email addy was here> sender rejected. Please verify that your email address is correct in your account settings and try again.
I tried creating a new outgoing server using the info from the tech support person and making that the default, but the exact same problem occurred. HELP please!
Chosen solution
So 91.3.0 helped? (you would have previously been on 91.2.1)
Read this answer in context 👍 0All Replies (20)
Hmm, can't seem to edit that post so I'll reply to my own...to be clear, all incoming email works just fine.
Use the information in my blog post to create a log of the outgoing attempt and post it here in support. Then we can talk about specific issues. \https://thunderbirdtweaks.blogspot.com/2021/10/logging-mail-sending-in-thunderbird.html
Please excuse the email addy, had to dig up one I don't use anymore and can delete after it gets shown in public. Here's the log...
mailnews.smtp: Sending message <ccd69d26-7e87-47de-4112-8f5a2e40927e@shaw.ca> SmtpService.jsm:84:18 mailnews.smtp: S: 220 shw-obgw-4001a.ext.cloudfilter.net cmsmtp ESMTP server ready
SmtpClient.jsm:429:17 mailnews.smtp: C: EHLO [192.168.0.10] SmtpClient.jsm:600:19 mailnews.smtp: S: 250-shw-obgw-4001a.ext.cloudfilter.net hello [24.80.177.200], pleased to meet you
250-AUTH LOGIN PLAIN
250-SIZE 30000000
250-8BITMIME
250-STARTTLS
250 OK
SmtpClient.jsm:429:17 mailnews.smtp: Possible auth methods: SmtpClient.jsm:948:17 mailnews.smtp: Maximum allowed message size: 30000000 SmtpClient.jsm:954:19 mailnews.smtp: C: MAIL FROM:<whipsncuffs@shaw.ca> BODY=8BITMIME SIZE=425 SmtpClient.jsm:600:19 mailnews.smtp: S: 550 <whipsncuffs@shaw.ca> sender rejected
SmtpClient.jsm:429:17 mailnews.smtp: Command failed: 550 <whipsncuffs@shaw.ca> sender rejected; currentAction=_actionMAIL SmtpClient.jsm:520:19 mailnews.send: Sending failed; An error occurred while sending mail. The mail server responded: <whipsncuffs@shaw.ca> sender rejected. Please verify that your email address is correct in your account settings and try again., exitCode=2153066722, originalMsgURI= MessageSend.jsm:321:27 mailnews.smtp: Closing connection... 2 SmtpClient.jsm:173:17 mailnews.smtp: Socket closed. SmtpClient.jsm:503:17
And here's the log after trying setting the jsmodule line to false as it didn't solve the problem.
mailnews.smtp: Sending message <2fee20be-03aa-cd9a-9b4d-462cd5753e21@shaw.ca> SmtpService.jsm:84:18 mailnews.smtp: S: 220 shw-obgw-4002a.ext.cloudfilter.net cmsmtp ESMTP server ready
SmtpClient.jsm:429:17 mailnews.smtp: C: EHLO [192.168.0.10] SmtpClient.jsm:600:19 mailnews.smtp: S: 250-shw-obgw-4002a.ext.cloudfilter.net hello [24.80.177.200], pleased to meet you
250-AUTH LOGIN PLAIN
250-SIZE 30000000
250-8BITMIME
250-STARTTLS
250 OK
SmtpClient.jsm:429:17 mailnews.smtp: Possible auth methods: SmtpClient.jsm:948:17 mailnews.smtp: Maximum allowed message size: 30000000 SmtpClient.jsm:954:19 mailnews.smtp: C: MAIL FROM:<whipsncuffs@shaw.ca> BODY=8BITMIME SIZE=425 SmtpClient.jsm:600:19 mailnews.smtp: S: 550 <whipsncuffs@shaw.ca> sender rejected
SmtpClient.jsm:429:17 mailnews.smtp: Command failed: 550 <whipsncuffs@shaw.ca> sender rejected; currentAction=_actionMAIL SmtpClient.jsm:520:19 mailnews.send: Sending failed; An error occurred while sending mail. The mail server responded: <whipsncuffs@shaw.ca> sender rejected. Please verify that your email address is correct in your account settings and try again., exitCode=2153066722, originalMsgURI= MessageSend.jsm:321:27 mailnews.smtp: Closing connection... 2 SmtpClient.jsm:173:17 mailnews.smtp: Socket closed. SmtpClient.jsm:503:17
and the message is still the same.
<whipsncuffs@shaw.ca> sender rejected. Please verify that your email address is correct in your account settings and try again
Shaw is refusing to accept mail from that address. Which leaves me with two questions.
- Does the shaw email address you are trying to send from actually exist. OR are you trying to send non Shaw email addresses via shaw. Something they refuse as a matter of course.
- Is your outgoing server (SMTP) entry for shaw correctly configured to use a password?
I have changed nothing. I have 4 email addresses that I have been running for decades. 3 I use regularly and that one which I don't. All 4 of them check messages successfully, including that one.
Just to make sure that one was still working, I went into shaw's online email program and sent one to that address, and Thunderbird downloaded it no problem.
So, whipsncuffs@shaw.ca as well as all 3 of the others will download but not upload. None of my settings have changed in years. As of last night I was sending emails successfully. Once Thunderbird updated to 91, I get what is logged above.
Sorry, I didn't reply directly to your second point. Is it configured correctly to use a password? I have no idea. I don't think my settings have changed in over a decade, so it's possible something needs to be tweaked.
Ah crap, I seem to have accidentally lied to you. There WAS a change to my settings. I hadn't changed back to my original outgoing server after spending time with Shaw support earlier. Im getting the exact same message, but here's a log with it changed back to what I was using last night.
jsmodule OFF
window.controllers/Controllers is deprecated. Do not use it for UA detection. blank NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIAutoCompleteInput.popup] LoginManagerChild.jsm:194 Element.releaseCapture() is deprecated. Use Element.releasePointerCapture() instead. For more help https://developer.mozilla.org/docs/Web/API/Element/releasePointerCapture menupopup.js:163:13 mailnews.smtp: Sending message <0a387333-d672-0110-ac93-666097a6191c@shaw.ca> SmtpService.jsm:84:18 mailnews.smtp: S: 220 shw-obgw-4001a.ext.cloudfilter.net cmsmtp ESMTP server ready
SmtpClient.jsm:429:17 mailnews.smtp: C: EHLO [192.168.0.10] SmtpClient.jsm:600:19 mailnews.smtp: S: 250-shw-obgw-4001a.ext.cloudfilter.net hello [24.80.177.200], pleased to meet you
250-AUTH LOGIN PLAIN
250-SIZE 30000000
250-8BITMIME
250-STARTTLS
250 OK
SmtpClient.jsm:429:17 mailnews.smtp: Possible auth methods: SmtpClient.jsm:948:17 mailnews.smtp: Maximum allowed message size: 30000000 SmtpClient.jsm:954:19 mailnews.smtp: C: MAIL FROM:<whipsncuffs@shaw.ca> BODY=8BITMIME SIZE=419 SmtpClient.jsm:600:19 mailnews.smtp: S: 550 <whipsncuffs@shaw.ca> sender rejected
SmtpClient.jsm:429:17 mailnews.smtp: Command failed: 550 <whipsncuffs@shaw.ca> sender rejected; currentAction=_actionMAIL SmtpClient.jsm:520:19 mailnews.send: Sending failed; An error occurred while sending mail. The mail server responded: <whipsncuffs@shaw.ca> sender rejected. Please verify that your email address is correct in your account settings and try again., exitCode=2153066722, originalMsgURI= MessageSend.jsm:321:27 mailnews.smtp: Closing connection... 2 SmtpClient.jsm:173:17 mailnews.smtp: Socket closed. SmtpClient.jsm:503:17
jsmodule ON
mailnews.smtp: Sending message <6c7e3e3f-5559-1344-4fe2-9290590f65d8@shaw.ca> SmtpService.jsm:84:18 mailnews.smtp: S: 220 shw-obgw-4004a.ext.cloudfilter.net cmsmtp ESMTP server ready
SmtpClient.jsm:429:17 mailnews.smtp: C: EHLO [192.168.0.10] SmtpClient.jsm:600:19 mailnews.smtp: S: 250-shw-obgw-4004a.ext.cloudfilter.net hello [24.80.177.200], pleased to meet you
250-AUTH LOGIN PLAIN
250-SIZE 30000000
250-8BITMIME
250-STARTTLS
250 OK
SmtpClient.jsm:429:17 mailnews.smtp: Possible auth methods: SmtpClient.jsm:948:17 mailnews.smtp: Maximum allowed message size: 30000000 SmtpClient.jsm:954:19 mailnews.smtp: C: MAIL FROM:<whipsncuffs@shaw.ca> BODY=8BITMIME SIZE=419 SmtpClient.jsm:600:19 mailnews.smtp: S: 550 <whipsncuffs@shaw.ca> sender rejected
SmtpClient.jsm:429:17 mailnews.smtp: Command failed: 550 <whipsncuffs@shaw.ca> sender rejected; currentAction=_actionMAIL SmtpClient.jsm:520:19 mailnews.send: Sending failed; An error occurred while sending mail. The mail server responded: <whipsncuffs@shaw.ca> sender rejected. Please verify that your email address is correct in your account settings and try again., exitCode=2153066722, originalMsgURI= MessageSend.jsm:321:27 mailnews.smtp: Closing connection... 2 SmtpClient.jsm:173:17 mailnews.smtp: Socket closed. SmtpClient.jsm:503:17
To be clear....changing back was simply a matter of setting the outgoing server 'default' back to the old one. I haven't touched the settings inside that selection. I created a new one to use when I was working with Shaw.
The correct settings for the Shaw smtp are: mail.shaw.ca on port 587, STARTTLS, normal password, User Name = part of address before @.
Thanks sfhowes, I went back and re-opened the smtp one I was using with the Shaw tech earlier. The only difference was STARTTLS and explaining to me what "name" meant. So I tried that version and got the exact same error.
Here's the log for what it did with those settings with jmodule on. I get the same message with jmodule off but didn't want to double log again as it feels kinda spammy.
Element.releaseCapture() is deprecated. Use Element.releasePointerCapture() instead. For more help https://developer.mozilla.org/docs/Web/API/Element/releasePointerCapture menupopup.js:163:13 NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIAutoCompleteInput.popup] LoginManagerChild.jsm:194 mailnews.smtp: Sending message <3041188b-f510-ff43-398e-59ec0f20e551@shaw.ca> SmtpService.jsm:84:18 mailnews.smtp: S: 220 shw-obgw-4001a.ext.cloudfilter.net cmsmtp ESMTP server ready
SmtpClient.jsm:429:17 mailnews.smtp: C: EHLO [192.168.0.10] SmtpClient.jsm:600:19 mailnews.smtp: S: 250-shw-obgw-4001a.ext.cloudfilter.net hello [24.80.177.200], pleased to meet you
250-AUTH LOGIN PLAIN
250-SIZE 30000000
250-8BITMIME
250-STARTTLS
250 OK
SmtpClient.jsm:429:17 mailnews.smtp: Possible auth methods: SmtpClient.jsm:948:17 mailnews.smtp: Maximum allowed message size: 30000000 SmtpClient.jsm:954:19 mailnews.smtp: C: MAIL FROM:<whipsncuffs@shaw.ca> BODY=8BITMIME SIZE=419 SmtpClient.jsm:600:19 mailnews.smtp: S: 550 <whipsncuffs@shaw.ca> sender rejected
SmtpClient.jsm:429:17 mailnews.smtp: Command failed: 550 <whipsncuffs@shaw.ca> sender rejected; currentAction=_actionMAIL SmtpClient.jsm:520:19 mailnews.send: Sending failed; An error occurred while sending mail. The mail server responded: <whipsncuffs@shaw.ca> sender rejected. Please verify that your email address is correct in your account settings and try again., exitCode=2153066722, originalMsgURI= MessageSend.jsm:321:27 mailnews.smtp: Closing connection... 2 SmtpClient.jsm:173:17 mailnews.smtp: Socket closed. SmtpClient.jsm:503:17
Despite your assertions, the response in the log you post says.
mailnews.smtp: Command failed: 550 <whipsncuffs@shaw.ca> sender rejected;
Any time a three digit code appears it is a direct error from the server. In this case it is very clear. 550 <whipsncuffs@shaw.ca> sender rejected; Shaw is rejecting that sender address, not Thunderbird.
I notice that their outgoing server appears to be with the cloudfilter.net organization. Why outgoing mail is being filtered by an incoming mail filter I have no idea. But it leaves me wondering.
However there are a couple of things to try.
Open the config editor and change the value of mailnews.send.jsmodule to false. Does send work for you then. Note this is not a solution, only a diagnostic.
Changing that value to false doesn't help. I believe you that the server is rejecting it, but I have no idea why. I have sent email on Shaw's webmail page from whipsncuffs to whipsncuffs and Thunderbird downloaded it earlier today. Hell, if you want, send an email to that addy from a junk account with some string of letters in it and I'll repost them here. Or give me a junk email to send to and I'll send to it from there using shaw's online webmail page. That account has been active for decades and still is, I just haven't used it for anything since my bygone days of online dating.
I'm so frustrated. I went to bed last night and everything worked. Thunderbird updates and now I can only receive.
I appreciate you taking the time to try to help me so far. I'm terrified of having to look into other methods of email. I used to use Outlook express and when it died a Shaw person suggested Thunderbird and I've used it ever since. It was similar enough in look and feel back then that transitioning was easy, plus it copied over all my years email data. Now I've got something like 30 years of saved emails in Thunderbird.
If you have any other suggestions I'm all ears. Tomorrow I'll try Shaw again on the off chance that it's their fault or something. For now I need sleep.
Is the password for this account 'weak' or 'strong'? I think if you connect to a secure server with a desktop client, the password has to be strong. If it isn't, change it on the Shaw site, remove the old password from Saved Passwords in Preferences, restart TB, enter the new, strong password when prompted.
Weak passwords might work with webmail, but not with IMAP, POP and SMTP.
I suppose I can try changing passwords, but I can't see how that would make a difference in this case. I still get incoming email in Thunderbird, and I could send the night before 91 installed. But I'll try it after breakfast just in case. Every suggestion is worth trying.
Is there some way I can revert to the earlier version and then just turn off updates?
I don't think your issue is related to the TB version, but if you install an earlier version and try to open a profile that was used in 91, you must start Profile Manager by opening a Run window (Winkey+R) and type
thunderbird.exe -p --allow-downgrade
Thunderbird 91 has a new sending routine, changing that value reverts to the V78 routine. As it did not help change it back, in a next release it might cause issues because it will be removed from the code by then. It also basically removes almost everything that is different V78 to 91. The only remaining difference I am aware of is submission uses UNICODE now. (It has been the defacto standard for text on the internet since Windows XP. But it is possible your provider does not support it.
Try sending mail to devilsgatedrive@gmail.com and matt_AU at gmx.com and see if either of those work. Just to be sure it is not just your test addresses :)
There is a remote possibility that they do not support 8bit encoding, despite the log from the server showing such support. (yahoo do not and used to say they did.) but that should not affect the refusal to accept the address.
WOOOOHOOO!!! Just as I went to Thunderbird to try sending the email you suggested Matt, Thunderbird informed me it had an update and needed to restart. After the restart I crossed my fingers and tried my own email addy's again. And they worked! Sent email to a friend, and it seems to have worked (he's not home to check, but it's in my 'sent' folder now). So, I guess the devs here fixed whatever the underlying cause was.
Thank you ever so much for the time you invested with me. I'm still going to send one from whips to you anyway, just to prove to you that it exists. :D
Sfhowes, thank you for your info too, but it looks like (at least for now) I can just continue with the patched version.
The sending email message box now says something about "Filter" but it goes by so fast that I'm not sure exactly what it says. So, they've added something, and I'm thrilled!
Modified
Chosen Solution
So 91.3.0 helped? (you would have previously been on 91.2.1)
Yes, 91.3.0 solved all my problems.