Closed Bug 267642 Opened 20 years ago Closed 20 years ago

Using "Send later" with non-existent Unsent folder produces just bogus error message and loses e-mail

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: nospam, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913 During creating and deleting of several new POP accounts, my prefs.js got messed up by Mozilla so that the unsent_folder_uri was pointing to a non-existent (already removed with one of the POP accounts) folder. When trying to use "Send later" feature, Mozilla always responded with "Could not copy message to your Sent folder", did not send the message, BUT copied it correctly to my main IMAP account's Sent folder. Obviously the message never reached the recepient without the user not knowing this, since the message correctly appeared in the Sent folder. Reproducible: Always Steps to Reproduce: 1. Since I don't know, when exactly Mozilla messed the prefs.js file itself, just try to simulate it: edit prefs.js by hand. 2. Put some wrong value for unsent_folder_uri (or similar, the spelling might be wrong). 3. Start up Mozilla/Mail, compose new message. 4. Press "Send later". Actual Results: You'll see an error message claiming the message could not be copied to SENT !!! folder. But in fact, message gets copied to Sent folder, but is never sent to the recepient. Expected Results: 1. Correct error message stating the problem is with "Unsent messages" folder. 2. Offer for either "Sending message immediately" or "Discarding the message". 3. Copying to the Sent folder occurs only after the message IS REALLY sent. Solution for this was hand-editing of prefs.js and removing the unsent_folder_uri line completely. Then on first start Mozilla asked, what should be done with Unsent messages and correctly associated Unsent messages folder with the one within Local folders. At best, under Mail & Newsgroups Accounts / Copies & Folders / should exist a UI which allows the user to change the folder for unsent messages. Since this: "Obviously the message never reached the recepient without the user not knowing this, since the message correctly appeared in the Sent folder." I put severity as major.
Forgot to mention the affected version of Mozilla/Mail is: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040913
Product: Browser → Seamonkey
Assignee: sspitzer → mail
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.