323673 - Not tolerant of null return code (SMTP)

Status: RESOLVED INCOMPLETE

(MailNews Core :: Networking: SMTP, defect)

Description

[kevin martin]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: ThunderBird 1.5 (20051201)

upgraded to tbird 1.5 on Thursday from 1.0.7 (installed tbird 1.5 in a completely fresh location but with my existing profile). When I send an email I now receive this message:

An error occured while sending mail. The mail server responded: . Please check the message and try again.

The account is setup to use authentication and TLS if available (still working on the sendmail side to get that setup). The funny thing is the mail is, in fact, sent, but tbird doesn't think so. Once I click OK on the Alert then the delivery sttaus box goes away and I'm back to the mail that I was sending. I've just been closing them after I discovered that the mail is, in fact, being sent.

This exact mail setup has worked flawlessly in tbird 1.0.3 - 1.0.7 so something got busted in 1.5.

Any help greatly appreciated...any further information I can safely provide I will be happy to.

here's more information from a tbird smtp log:

1086829856[8c1ceb0]: SMTP Connecting to: localhost
1086829856[8c1ceb0]: SMTP entering state: 0
1086829856[8c1ceb0]: SMTP Response: 220 localhost ESMTP Sendmail 8.13.4/8.13.4; Fri, 13 Jan 2006 15:01:54 -0600
1086829856[8c1ceb0]: SMTP entering state: 15
1086829856[8c1ceb0]: SMTP Send: EHLO [192.168.0.2]
1086829856[8c1ceb0]: SMTP entering state: 0
1086829856[8c1ceb0]: SMTP Response: 250-localhost Hello [69.222.20.30], pleased to meet you
1086829856[8c1ceb0]: SMTP entering state: 0
1086829856[8c1ceb0]: SMTP Response: 250-ENHANCEDSTATUSCODES
1086829856[8c1ceb0]: SMTP entering state: 0
1086829856[8c1ceb0]: SMTP Response: 250-PIPELINING
1086829856[8c1ceb0]: SMTP entering state: 0
1086829856[8c1ceb0]: SMTP Response: 250-EXPN
1086829856[8c1ceb0]: SMTP entering state: 0
1086829856[8c1ceb0]: SMTP Response: 250-VERB
1086829856[8c1ceb0]: SMTP entering state: 0
1086829856[8c1ceb0]: SMTP Response: 250-8BITMIME
1086829856[8c1ceb0]: SMTP entering state: 0
1086829856[8c1ceb0]: SMTP Response: 250-SIZE
1086829856[8c1ceb0]: SMTP entering state: 0
1086829856[8c1ceb0]: SMTP Response: 250-DSN
1086829856[8c1ceb0]: SMTP entering state: 0
1086829856[8c1ceb0]: SMTP Response: 250-ETRN
1086829856[8c1ceb0]: SMTP entering state: 0
1086829856[8c1ceb0]: SMTP Response: 250-AUTH LOGIN PLAIN
1086829856[8c1ceb0]: SMTP entering state: 0
1086829856[8c1ceb0]: SMTP Response: 250-DELIVERBY
1086829856[8c1ceb0]: SMTP entering state: 0
1086829856[8c1ceb0]: SMTP Response: 250 HELP
1086829856[8c1ceb0]: SMTP entering state: 4
1086829856[8c1ceb0]: SMTP entering state: 22
1086829856[8c1ceb0]: SMTP entering state: 17
1086829856[8c1ceb0]: Logging suppressed for this command (it probably contained authentication information)
1086829856[8c1ceb0]: SMTP entering state: 0
1086829856[8c1ceb0]: SMTP Response: 235 2.0.0 OK Authenticated
1086829856[8c1ceb0]: SMTP entering state: 19
1086829856[8c1ceb0]: SMTP entering state: 3
1086829856[8c1ceb0]: SMTP Send: MAIL FROM:<[e-mail]> SIZE=857
1086829856[8c1ceb0]: SMTP entering state: 0
1086829856[8c1ceb0]: SMTP Response: 250 2.1.0 <[e-mail]>... Sender ok
1086829856[8c1ceb0]: SMTP entering state: 6
1086829856[8c1ceb0]: SMTP Send: RCPT TO:<[e-mail]>
1086829856[8c1ceb0]: SMTP entering state: 0
1086829856[8c1ceb0]: SMTP Response: 250 2.1.5 <[e-mail]>... Recipient ok
1086829856[8c1ceb0]: SMTP entering state: 7
1086829856[8c1ceb0]: SMTP Send: DATA
1086829856[8c1ceb0]: SMTP entering state: 0
1086829856[8c1ceb0]: SMTP Response: 354 Enter mail, end with "." on a line by itself
1086829856[8c1ceb0]: SMTP entering state: 8
1086829856[8c1ceb0]: SMTP entering state: 9
1086829856[8c1ceb0]: SMTP Send: .
1086829856[8c1ceb0]: SMTP entering state: 0
1086829856[8c1ceb0]: SMTP Response:
1086829856[8c1ceb0]: SMTP entering state: 10
1086829856[8c1ceb0]: SMTP entering state: 12
1086829856[8c1ceb0]: SMTP entering state: 13

mailhost and sender/recipient stuff changed to protect the innocent...however, as you can see, there IS a "Response: " that comes back from the sendmail server. Here's what that looks like using Tbird 1.0.7:

1086667008[8cb1040]: SMTP Connecting to: localhost
1086667008[8cb1040]: SMTP entering state: 0
1086667008[8cb1040]: SMTP Response: 220 localhost ESMTP Sendmail 8.13.4/8.13.4; Fri, 13 Jan 2006 16:03:56 -0600
1086667008[8cb1040]: SMTP entering state: 15
1086667008[8cb1040]: SMTP Send: EHLO [192.168.0.2]
1086667008[8cb1040]: SMTP entering state: 0
1086667008[8cb1040]: SMTP Response: 250-localhost Hello [69.222.20.30], pleased to meet you
1086667008[8cb1040]: SMTP entering state: 0
1086667008[8cb1040]: SMTP Response: 250-ENHANCEDSTATUSCODES
1086667008[8cb1040]: SMTP entering state: 0
1086667008[8cb1040]: SMTP Response: 250-PIPELINING
1086667008[8cb1040]: SMTP entering state: 0
1086667008[8cb1040]: SMTP Response: 250-EXPN
1086667008[8cb1040]: SMTP entering state: 0
1086667008[8cb1040]: SMTP Response: 250-VERB
1086667008[8cb1040]: SMTP entering state: 0
1086667008[8cb1040]: SMTP Response: 250-8BITMIME
1086667008[8cb1040]: SMTP entering state: 0
1086667008[8cb1040]: SMTP Response: 250-SIZE
1086667008[8cb1040]: SMTP entering state: 0
1086667008[8cb1040]: SMTP Response: 250-DSN
1086667008[8cb1040]: SMTP entering state: 0
1086667008[8cb1040]: SMTP Response: 250-ETRN
1086667008[8cb1040]: SMTP entering state: 0
1086667008[8cb1040]: SMTP Response: 250-AUTH LOGIN PLAIN
1086667008[8cb1040]: SMTP entering state: 0
1086667008[8cb1040]: SMTP Response: 250-DELIVERBY
1086667008[8cb1040]: SMTP entering state: 0
1086667008[8cb1040]: SMTP Response: 250 HELP
1086667008[8cb1040]: SMTP entering state: 4
1086667008[8cb1040]: SMTP entering state: 22
1086667008[8cb1040]: SMTP entering state: 17
1086667008[8cb1040]: Logging suppressed for this command (it probably contained authentication information)
1086667008[8cb1040]: SMTP entering state: 0
1086667008[8cb1040]: SMTP Response: 235 2.0.0 OK Authenticated
1086667008[8cb1040]: SMTP entering state: 19
1086667008[8cb1040]: SMTP entering state: 3
1086667008[8cb1040]: SMTP Send: MAIL FROM:<[e-mail]> SIZE=2609
1086667008[8cb1040]: SMTP entering state: 0
1086667008[8cb1040]: SMTP Response: 250 2.1.0 <[e-mail]>... Sender ok
1086667008[8cb1040]: SMTP entering state: 6
1086667008[8cb1040]: SMTP Send: RCPT TO:<[e-mail]>
1086667008[8cb1040]: SMTP entering state: 0
1086667008[8cb1040]: SMTP Response: 250 2.1.5 <[e-mail]>... Recipient ok
1086667008[8cb1040]: SMTP entering state: 7
1086667008[8cb1040]: SMTP Send: DATA
1086667008[8cb1040]: SMTP entering state: 0
1086667008[8cb1040]: SMTP Response: 354 Enter mail, end with "." on a line by itself
1086667008[8cb1040]: SMTP entering state: 8
1086667008[8cb1040]: SMTP entering state: 9
1086667008[8cb1040]: SMTP Send: .
1086667008[8cb1040]: SMTP entering state: 0
1086667008[8cb1040]: SMTP Response:
1086667008[8cb1040]: SMTP entering state: 10
1086667008[8cb1040]: SMTP Send: QUIT
1086667008[8cb1040]: SMTP entering state: 0
1086667008[8cb1040]: SMTP entering state: 0
1086667008[8cb1040]: SMTP Response: ===== SENDALL: mode b, id k0DM3uJr010135, e_from 0x80d3e70=<[e-mail]>:
1086667008[8cb1040]: SMTP entering state: 11
1086667008[8cb1040]: SMTP entering state: 13

As we can see, 1.0.7 handles the empty response and just continues on it's merry way. This is a client issue, not a server issue.

I've also upgraded my sendmail to 8.13.5 and have the same issue still.   If more information needed please let me know what and how to capture.

Reproducible: Always

Steps to Reproduce:
1. Create new mail or reply to email
2. Click send.
3. Error occurs

Actual Results:  
Email is sent but tbird 1.5 reports error and doesn't close the compose window or save the sent mail to the Sent Items folder.

Expected Results:  
Mail sent, compose window closes, Sent Items populated with new message.

Using the ThunderStripe theme but using the default theme doesn't change what occurs.

Comment 1

[Philip Withnall (unavailable)]

Can you reproduce this when running Thunderbird in safe mode?

Comment 2

[WADA:World Anti-bad-Duping Agency]

(In reply to comment #0)
> As we can see, 1.0.7 handles the empty response and just continues on it's
> merry way. This is a client issue, not a server issue.

Just F.Y.I.
RFC 2821 clearly defines reply ;
(Reply : http://rfc.net/rfc2821.html#s2.3.11)
> The general form of a reply is a numeric completion code
> (indicating failure or success) usually followed by a text string.
(SMTP Reply : http://rfc.net/rfc2821.html#s4.2)
> An SMTP reply consists of a three digit number (transmitted as three
> numeric characters) followed by some text unless specified otherwise
> in this document.   
I couldn't find description about null completion code case.

I never deny request for torelance when error/violation/fault/unclearness is involved, and I think that Tb should be torelant for null reply code, including null reply code and null text string case.
And I believe it's regression over 1.0.x, because Tb 1.0.x was torelant for null reply code.
But I think, if possible, you'd better to setup your Sendmail safely(reply code of 250 when OK reply), in addition to requesting mail client software developer for torelance, because you are owner of the mail server.

Comment 3

[Philip Withnall (unavailable)]

Confirming.

Comment 4

[Wayne Mery (:wsmwk)]

Kevin can you test with version 3?  (I don't know that this has been fixed or not)
Marking regression per wada's comment 2

Comment 5

[Wayne Mery (:wsmwk)]

Version 91 has all new smtp backend code. If you can still reproduce this issue, please file a new bug report https://bugzilla.mozilla.org/enter_bug.cgi?product=MailNews%20Core&component=Networking%3A%20SMTP