Under build id 2004042721, I attempted to use the SMTP server at mail.com (smtp1.mail.com) to send an outgoing message. Using ethereal, the TCP stream shows the server indicating an authorization failure. The dialogue is reproduced below. After the failure, no indication was given that the message could not be delivered due to an authorization failure. Thus, I was led to believe that it had been sent successfully. 220 smtp1.us4.outblaze.com ESMTP EHLO programmer.net 250-smtp1.us4.outblaze.com 250-AUTH=LOGIN 250-PIPELINING 250 8BITMIME AUTH LOGIN aHVtbWluZ2JpcmQ= 334 UGFzc3dvcmQ6 TElnTWhETGg= 535 auth failure

reassign to mscott

I see this on 1.0 on Linux. This bug causes dataloss, because the mail appears to be sent but isn't. It should probably have a higher severity because of this.

I tested this and I found that the SMTP server closes the connection if the login is wrong. It does not wait for the client to quit. Maybe this is the reason why mozilla does not show a message that the send has failed.

My SMTP server does the same thing, closes the connection if the user's authentication fails. I don't have a server handy that keeps the connection open to see if this is related or not.

I tested it with the original posters SMTP server smtp1.us4.outblaze.com. When I use a SMTP server that does not close the connection, mozilla prompts again for the password.

I switched on the log for nsSmtpProtocol.cpp and these are the last 2 protocol machine states: 21 SMTP_AUTH_PROCESS_STATE 16 SMTP_SEND_AUTH_LOGIN_USERNAME and a suppressed line which is the SendData of the login information. Thats it. No SMTP_DONE or SMTP_ERROR_DONE.

reassigning to nbaca

Is this still open???

(In reply to comment #8) > Is this still open??? Moritz, does this happen to you?

(In reply to comment #9) > > Moritz, does this happen to you? > No, I expected it to be closed. That's why I asked. Probably it would be closed by now automaticly if I hadn't done so, but by that time there was no automtic closing and I do not have the right to do so.

Which server did you use for testing? smtp1.us4.outblaze.com does no longer behave like in the initial posting. It does not close the connection if authorization fails.

WFM per Morty. If you see otherwise please reopen and attach log. instructions: http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html to recap - SMTP server closes the connection if login fails and does not wait for the client to quit.