Closed Bug 47324 Opened 21 years ago Closed 21 years ago

Not sending EHLO after having error with saving to sent folder

Categories

(MailNews Core :: Networking: SMTP, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: bugzilla, Assigned: mscott)

Details

(Whiteboard: [nsbeta3+])

Attachments

(1 file)

If you set up your IMAP sent folder to a bogus folder and compose a mail and 
press Send, the mail gets send and you get an error saying "you send operation 
went fine, but unable to save to sent folder....". In this dialog press Ok and 
return to the Compose dialog.
Now press Send againg and you get this error:
"An error occurred while sending mail. The mail server responded: Polite people 
say HELO first. Please verify that you email address is correct in you Mail 
prefereces and try again."

Im attaching the SMTP log...
ahh looks like someone is holding onto the smtp protocol instance and we try to
reuse it. This may be causing some of the other EHLO/HELO errors I have bugs
about. This is bad.
Status: NEW → ASSIGNED
Keywords: correctness, nsbeta3
Target Milestone: --- → M18
Keywords: relnote2
Just a note that the first SMTP transaction is correct but all subsequent ones
forget to say EHLO, at least that's what happens on Linux.

My sendmail does not return an error to the sending client but does make a
syslog entry and also adds a header like this:

X-Authentication-Warning: darkstar.frop.org:
        localhost [127.0.0.1] didn't use HELO protocol

to the message so all recipients know Mozilla screwed up. Many will assume the
sender is a spammer. Not good at all.
Keywords: mail2
I have a fix for this. 
.
Whiteboard: [nsbeta3+]
Fix checked in. 
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
QA Contact: lchiang → huang
Now I'm not getting the "EHLO" error anymore, but something is still very wrong.
The error lies in bug 47311.
Status: RESOLVED → VERIFIED
removing mail2 keyword.
Keywords: mail2
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.