Bugzilla

So here's a new twist. I saw gene's mention that it worked for him today from his ISP in comment 71. I once again tried to see what would happen using 82.0a from 5-16-2020 but it failed. Then it auto updated itself to 90.0a from 29-5-2021 and failed again.

Then I wondered: What happens if I try to send from Thunderbird@familie-leininger.at to my gmail.com address. I got a bit of a different server response in 90.0a. It's saying I was spamming but that the recipient was "(null)". Obviously not but...huh?

Below is what 90.a spit out in error console.

Prompter: internal dialogs not available in this context. Falling back to window prompt. Prompter.jsm:1084
mailnews.smtp: Socket timed out. SmtpClient.jsm:512:17
mailnews.smtp: Command failed: 451 Sorry, you are spamming!; currentAction=_actionRCPT SmtpClient.jsm:502:19
mailnews.smtp: RCPT TO failed for: <removed_to_prevent_spam>@gmail.com SmtpClient.jsm:1191:19
mailnews.smtp: Can't send mail - all recipients were rejected SmtpClient.jsm:1204:21
mailnews.send: Sending failed; An error occurred while sending mail. The mail server responded:
Sorry, you are spamming!.
Please check the message recipient "(null)" and try again., exitCode=2153066783, originalMsgURI= MessageSend.jsm:321:27
Prompter: internal dialogs not available in this context. Falling back to window prompt. Prompter.jsm:1084

So at this point, I went back and set up 82.0a 5-16-2020 again, made sure it couldn't auto-update to 90.0a and, again, tried to send to my gmail.com account. Error Console spit out nothing at all but I got the error message "An error occurred while sending mail. The mail server responded: Sorry, you are spamming!. Please check the message recipient "<removed_to_prevent_spam>@gmail.com" and try again." So, unlike what 90.0a did, it wasn't a "(null)" recipient like 90.0a.

I'm not trying to go off reservation with this new info but its' weird for sure and just wanted to share this result.

So here's a new twist. I saw gene's mention that it worked for him today from his ISP in comment 71. I once again tried to see what would happen using 82.0a from 5-16-2020 but it failed. Then it auto updated itself to 90.0a from 29-5-2021 and failed again.

Then I wondered: What happens if I try to send from Thunderbird@familie-leininger.at to my gmail.com address. I got a bit of a different server response in 90.0a. It's saying I was spamming but that the recipient was "(null)". Obviously not but...huh?

Below is what 90.a spit out in error console.

Prompter: internal dialogs not available in this context. Falling back to window prompt. Prompter.jsm:1084
mailnews.smtp: Socket timed out. SmtpClient.jsm:512:17
mailnews.smtp: Command failed: 451 Sorry, you are spamming!; currentAction=_actionRCPT SmtpClient.jsm:502:19
mailnews.smtp: RCPT TO failed for: <removed_to_prevent_spam>@gmail.com SmtpClient.jsm:1191:19
mailnews.smtp: Can't send mail - all recipients were rejected SmtpClient.jsm:1204:21
mailnews.send: Sending failed; An error occurred while sending mail. The mail server responded:
Sorry, you are spamming!.
Please check the message recipient "(null)" and try again., exitCode=2153066783, originalMsgURI= MessageSend.jsm:321:27
Prompter: internal dialogs not available in this context. Falling back to window prompt. Prompter.jsm:1084

So at this point, I went back and set up 82.0a 5-16-2020 again, made sure it couldn't auto-update to 90.0a and, again, tried to send to my gmail.com account. Error Console spit out nothing at all but I got the error message "An error occurred while sending mail. The mail server responded: Sorry, you are spamming!. Please check the message recipient "<removed_to_prevent_spam>@gmail.com" and try again." So, unlike what 90.0a did, it wasn't a "(null)" recipient like 90.0a.

I'm not trying to go off the reservation with this new info but its' weird for sure and just wanted to share this result.

So here's a new twist. I saw gene's mention that it worked for him today from his ISP in comment 71. I once again tried to see what would happen using 82.0a from 5-16-2020 but it failed. Then it auto updated itself to 90.0a from 29-5-2021 and failed again.

Then I wondered: What happens if I try to send from Thunderbird@familie-leininger.at to my gmail.com address. I got a bit of a different server response in 90.0a. It's saying I was spamming but that the recipient was "(null)". Obviously not but...huh?

Below is what 90.a spit out in error console.

Prompter: internal dialogs not available in this context. Falling back to window prompt. Prompter.jsm:1084
mailnews.smtp: Socket timed out. SmtpClient.jsm:512:17
mailnews.smtp: Command failed: 451 Sorry, you are spamming!; currentAction=_actionRCPT SmtpClient.jsm:502:19
mailnews.smtp: RCPT TO failed for: <removed_to_prevent_spam>@gmail.com SmtpClient.jsm:1191:19
mailnews.smtp: Can't send mail - all recipients were rejected SmtpClient.jsm:1204:21
mailnews.send: Sending failed; An error occurred while sending mail. The mail server responded:
Sorry, you are spamming!.
Please check the message recipient "(null)" and try again., exitCode=2153066783, originalMsgURI= MessageSend.jsm:321:27
Prompter: internal dialogs not available in this context. Falling back to window prompt. Prompter.jsm:1084

So at this point, I went back and set up 82.0a 5-16-2020 again, made sure it couldn't auto-update to 90.0a and, again, tried to send to my gmail.com account. Error Console spit out nothing at all but I got the error message "An error occurred while sending mail. The mail server responded: Sorry, you are spamming!. Please check the message recipient "<removed_to_prevent_spam>@gmail.com" and try again." So, unlike what 90.0a did, it wasn't a "(null)" recipient like 90.0a.

I'm not trying to go off the reservation with this new info but it's weird for sure and just wanted to share this result.