864 bytes, text/plain
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla 1.3 The SMTP connection appears to send the mail, but an error appears indicating that the SMTP connection has failed. Attempts to re-send the message may or may not generate the same warnings. In fact, the SMTP connection has sent the message, as many times as you've tried, but the mail message is not saved into the remote SENT folder. All folders are IMAP. Eventually, after several retries, the SEND operations appears to work and the sent message is saved in my SENT folder. I then get many emails from colleages nagging me for sending them several copies of an email. Reproducible: Always Steps to Reproduce: 1. Compose a new, or reply to, an email message. 2. Type in your message, address the message, etc. 3. Hit "Send". 4. Wait for errors and follow the "retry" instructions, sending many emails and annoying colleages. Eventually it will work. Actual Results: Read "Details" section. Expected Results: Sent the email and saved a copy it in my SENT folder ... on the first attempt!!! Version 1.2.1 (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130) works well. The new version 1.3 that I downloaded on 2002-03-13 does not work.
*** Bug 211661 has been marked as a duplicate of this bug. ***
Whoops. My comment #1 above was an accident I made when I marked another bug wrongfully as a duplicate of this one.
Created attachment 140750 [details] Sample of what a testcase SMTP session would look like This is easy to duplicate.. if, after the mail is sent, the ISP closes the session instead of waiting for Mozilla to close it, Mozilla throws a tantrum, but it has already said that the mail was sent. it does not close the mail composer window and it does not put it in the Sent folder. This is an example of an SMTP server session for which Mozilla would have this problem.
This has been seen by me on macOS-X and FreeBSD in addition to PC I see it on Mozilla 1.4 and 1.6. so should be OS= ALL
smtp.sbcglobal.net hangs up on me after the data section now. They just started doing it. I get this error in mozilla 1.4 and 1.6. SBC refuses to fix the smtp issue in sendmail. Does anyone know if this happens in NS4/6/7? 220 pimout4-ext.prodigy.net ESMTP Sendmail 8.12.10 out 1msg/8.12.10; Tue, 10 Feb 2004 00:06:44 -0500 HELO adsl-64-161-176-181.dsl.lsan03.pacbell.net. 250 pimout4-ext.prodigy.net Hello adsl-64-161-176-181.dsl.lsan03.pacbell.net [64 .161.176.181], pleased to meet you MAIL FROM:firstname.lastname@example.org 250 2.1.0 email@example.com... Sender ok RCPT TO:firstname.lastname@example.org 250 2.1.5 email@example.com... Recipient ok DATA 354 Enter mail, end with "." on a line by itself This is a test . 250 2.0.0 i1A56ipw194316 Message accepted for delivery Connection to host lost.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.