Message not saved if failing via "Relaying disallowed" with 553
Categories
(MailNews Core :: Networking: SMTP, defect)
Tracking
(Not tracked)
People
(Reporter: mozilla, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:86.0) Gecko/20100101 Firefox/86.0
Steps to reproduce:
Create a message
Change "From" to "Customize 'From' address"
Change "From" to a non-relayable address
choose an arbitrary "to" recipient
Click "Send"
Actual results:
From the SMTP Server, I get an error:
"An error occurred while sending mail. The mail server responded: Relaying disallowed as xxx@yyy.zzz. Please check the message and try again."
When I close the error message, the email message closes, and cannot be found in Drafts, Sent or Outbox. The message appears lost.
Expected results:
The message should have stayed open, ready to edit the 'From' Address to a different value.
I can reproduce this readily on some servers.
Here is an SMTP log for a failure that does not close the unsent message (Working correctly):
2021-03-10 17:26:13.094000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP entering state: 0
2021-03-10 17:26:13.094000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP Response: 235 Authentication succeeded
2021-03-10 17:26:13.094000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP entering state: 18
2021-03-10 17:26:13.094000 UTC - [(null) 9240: Main Thread]: D/SMTP SMTP Login response, code 235
2021-03-10 17:26:13.094000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP entering state: 3
2021-03-10 17:26:13.094000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP Send: MAIL FROM:<test@example.com> BODY=8BITMIME SIZE=416
2021-03-10 17:26:13.266000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP entering state: 0
2021-03-10 17:26:13.266000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP Response: 250 OK
2021-03-10 17:26:13.266000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP entering state: 5
2021-03-10 17:26:13.266000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP Send: RCPT TO:<dan@example.com>
2021-03-10 17:26:13.445000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP entering state: 0
2021-03-10 17:26:13.445000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP Response: 250 Accepted
2021-03-10 17:26:13.445000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP entering state: 6
2021-03-10 17:26:13.445000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP Send: DATA
2021-03-10 17:26:13.623000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP entering state: 0
2021-03-10 17:26:13.623000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP Response: 354 Enter message, ending with "." on a line by itself
2021-03-10 17:26:13.623000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP entering state: 7
2021-03-10 17:26:13.623000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP entering state: 8
2021-03-10 17:26:13.624000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP Send: .
2021-03-10 17:26:13.811000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP entering state: 0
2021-03-10 17:26:13.811000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP Response: 550 Invalid From address.
2021-03-10 17:26:13.811000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP entering state: 9
2021-03-10 17:26:16.672000 UTC - [(null) 9240: Main Thread]: I/SMTP SMTP Send: QUIT
Here is an SMTP log for a failure that closes and loses the unsent message (BUG):
2021-03-10 17:20:20.150000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP Response: 235 Authentication Successful
2021-03-10 17:20:20.150000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP entering state: 18
2021-03-10 17:20:20.150000 UTC - [(null) 11688: Main Thread]: D/SMTP SMTP Login response, code 235
2021-03-10 17:20:20.150000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP entering state: 3
2021-03-10 17:20:20.150000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP Send: MAIL FROM:<test@example.com> SIZE=927
2021-03-10 17:20:20.203000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP entering state: 0
2021-03-10 17:20:20.203000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP Response: 250 Sender <test@example.com> OK
2021-03-10 17:20:20.203000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP entering state: 5
2021-03-10 17:20:20.203000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP Send: RCPT TO:<dan@example.com>
2021-03-10 17:20:20.257000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP entering state: 0
2021-03-10 17:20:20.257000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP Response: 250 Recipient <dan@example.com> OK
2021-03-10 17:20:20.257000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP entering state: 6
2021-03-10 17:20:20.257000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP Send: DATA
2021-03-10 17:20:20.311000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP entering state: 0
2021-03-10 17:20:20.311000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP Response: 354 Ok Send data ending with <CRLF>.<CRLF>
2021-03-10 17:20:20.311000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP entering state: 7
2021-03-10 17:20:20.311000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP entering state: 8
2021-03-10 17:20:20.311000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP Send: .
2021-03-10 17:20:20.371000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP entering state: 0
2021-03-10 17:20:20.371000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP Response: 553 Relaying disallowed as test@example.com
2021-03-10 17:20:20.371000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP entering state: 9
2021-03-10 17:20:25.502000 UTC - [(null) 11688: Main Thread]: I/SMTP SMTP Send: QUIT
It would seem that the only significant difference is the final response code. On the failed-but-not-deleted server, the code is 550, but on the failed-and-deleted server, the response code is 553.
That would seem to suggest that 553 is closing and removing/deleting/losing the message incorrectly. Good starting point anyway.
Lost YET ANOTHER long-written email because of this bug today.
Comment 3•4 years ago
|
||
Sorry for your loss.
When was the last time this worked for you?
Does this help explain why you get the error?
Haha thanks. We're all in mourning.
I appreciate the link, I'm sure it's helpful.
This bug report is not about what's causing a "Relaying Denied" error.
The bug report is how Thunderbird reacts to getting a 553 in lieu of 550.
550 errors show the server's error message, but then leave the email message open, unsent, ready to fix my relay typo or save to drafts.
553 errors show the server's error message, but then the message closes, not saved in "Sent" or "Drafts" or even the "Outbox". All work lost.
Not sure this is EXACTLY the problem, but all my troubleshooting and research seem to point to it.
I left logs above demonstrating a 550 and 553, and how Thunderbird reacts to each.
Comment 5•4 years ago
|
||
Thanks,
This might be a better Product and Component.
Comment 7•4 years ago
|
||
alfadog,
Version 91 has all new smtp backend code. Can you reproduce this issue using version 91?
Updated•4 years ago
|
Hello, I confirmed the bug in 79? today, then upgraded to 91, and confirmed that the bug is gone!
Nice work!
Many Thanks!
Description
•