Closed Bug 211661 Opened 22 years ago Closed 22 years ago

Mozilla Mail 1.2.1 and 1.3 sorts messages into the Sent-folder although the

Categories

(MailNews Core :: Networking: SMTP, defect)

x86
All
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 189428

People

(Reporter: ep, Assigned: sspitzer)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030325 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030325 This happens when the server closes the socket, e.g. because the authentification failed. Here's an excerpt of the communication: client -> EHLO ******** server <- 250-***************** Hello [********], pleased to meet you server <- 250-ENHANCEDSTATUSCODES server <- 250-PIPELINING server <- 250-EXPN server <- 250-VERB server <- 250-8BITMIME server <- 250-SIZE server <- 250-DSN server <- 250-ETRN server <- 250-AUTH PLAIN LOGIN server <- 250-STARTTLS server <- 250-DELIVERBY server <- 250 HELP client -> AUTH PLAIN AbCdEfGhIjKlMn== server <- 535 5.7.0 authentication failed client -> AUTH PLAIN AbCdEfGhIjKlMn== server <- 535 5.7.0 authentication failed client -> AUTH PLAIN AbCdEfGhIjKlMn== server <- 535 5.7.0 authentication failed client -> AUTH PLAIN AbCdEfGhIjKlMn== server <- 535 5.7.0 authentication failed client -> AUTH PLAIN AbCdEfGhIjKlMn== server <- 535 5.7.0 authentication failed client -> AUTH PLAIN AbCdEfGhIjKlMn== server <- 535 5.7.0 authentication failed client -> AUTH PLAIN AbCdEfGhIjKlMn== server <- 535 5.7.0 authentication failed client -> AUTH PLAIN AbCdEfGhIjKlMn== server <- 535 5.7.0 authentication failed client -> AUTH PLAIN AbCdEfGhIjKlMn== -- server closes the socket -- This are *two* bugs: 1. Mozilla ignores the errorcode of the authentification 2. Mozilla pesumes the message has been delivered succesfully when the socket is closed (this is the behaviour also during the whole communication) and does not wait for the 250 return code of the DATA request. The result is, that the email is put to the sent box but was NEVER send out!!! Reproducible: Always Steps to Reproduce: 1.Send email 2. Have SMTP give funny answer as described above 3. Have email, which was not actually delivered sorted to the sent box Actual Results: the email is sorted to the sent box Expected Results: pop-up unable to send would be appropriate. We work with Linux/Windows Mozilla 1.2.1 and 1.3 and it happens on all of them. The problem is, if the SMTP is not repsonding correclty to Mozilla you don't send mail, but you thought you did. This is very very severe in a business enivironment, I don't have to explain any further.
If you need any help in reproducing or understanding what we mean, contact us. This is really a very severe bug, because now I am not anymore sure whether I sent out emails or not, even though they are in the send folder.
Summary: Mozilla Mail 1.2.1 and 1.3 sorts messages into the Sent-folder although the message has not been delivered. → Mozilla Mail 1.2.1 and 1.3 sorts messages into the Sent-folder although the message has not been delivered.
Marking a duplicate of bug 197447 and (not that it matters anymore <g>) changing status to major (could even be normal?) since it does not block development or testing of the product. *** This bug has been marked as a duplicate of 197447 ***
Severity: blocker → major
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Summary: Mozilla Mail 1.2.1 and 1.3 sorts messages into the Sent-folder although the message has not been delivered. → Mozilla Mail 1.2.1 and 1.3 sorts messages into the Sent-folder although the
Whoops. Marked a duplicate of the wrong bug (another one I was looking at). I'll have to try again. Reopening for now...
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Now I've got the right bug. :) Sorry for this mess... *** This bug has been marked as a duplicate of 189428 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → DUPLICATE
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.