Closed Bug 234587 Opened 22 years ago Closed 20 years ago

SMTP error causes thunderbird to hang

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: john, Assigned: mscott)

Details

User-Agent: Build Identifier: Thunderbird 0.4 (20031205) While attempting to send a mail message (with 27K HTML attachment FWIW) and with the 'Sending Messages ... Status: Sending Message / Progress: '(nothing) dialogue window still visible in the background I got a 'Send Message Error ... connecting to smtp server smtp.ntlworld.com failed ...' [OK]. However clicking OK had no effect and other parts of Thurnderbird were unresponsive including a read message window and the main window. Task manager showed all tbird processes as running (not 'not responding') and when I choose 'end Task' for the compose process responds 'The system cannot end this process because it is waiting for a response from you'. When I killed that all of thunderbird dies. When I tried again to send a similar message (the original having been lost when I killed TB) I got a the same Sending Messages and Send Message Error dialogues: the latter was again unresponsive but the former responded to a click on 'Cancel' and then clicking OK on the Send Message Error dialogue worked. I think - but am not sure - that I tried clicking cancel on the first occurrence of the problem. The 3rd time I tried the same error dialogue came up (my smtp server must be pansted right now) but this time clicking on OK in the error dialogue worked directly (no need to click cancel in the sending dialogue first) The time between getting the Sending Messages dialogue and the Send Message Error is about 20 seconds Reproducible: Couldn't Reproduce Steps to Reproduce: 1. Open message from inbox in new window 2. In this window Reply to the message, attaching a 27K file (in my case in html) and Send 3. make sure your smtp server is broken :-) Sounds to me similar to Bug 224197 but that's been fixed.
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
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.