Closed Bug 248607 Opened 20 years ago Closed 19 years ago

window says 'message not sent' when it actually is

Categories

(Thunderbird :: General, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: davidmaxwaterman, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040531 Firefox/0.8.0+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040531 Firefox/0.8.0+ When I press send on a compose window, it sends the email and then attempts to copy the message to the sent folder. Sometimes, it seems to hang when trying to copy if to the sent folder. If I click 'cancel', the progress window disappears, but the message window remains (this is misleading in itself, since I am tempted to send the message again). If I then close the window, a window pops up saying that the message has not been sent, when, in fact, it has. Using a remote (different country) IMAP server. Reproducible: Always Steps to Reproduce: 1.send message 2.click cancel after it has sent the message, but before it has copied it to the sent folder 3.close the window Actual Results: window appears claiming the message has not been sent Expected Results: window appears claiming it could not copy to sent folder
(In reply to comment #1) > Isn't this the same as or related to bug 277352 ? > https://bugzilla.mozilla.org/show_bug.cgi?id=277352 I would say that it is related, yes, but it is certainly not the same. That bug is complaining the failure to send. This bug is complaining only about the message saying the email wasn't sent, when it actually was. IMO this is a potentially critically misleading message which could cause a user to send many identical messages while thinking none had been sent.
To avoid bug spam, please see my answer here: http://forums.mozillazine.org/viewtopic.php?t=260485
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: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.