Build Date & Platform Bug Found: win32 commercial seamonkey build 2000-091409-m18 installed on P500 Win98 linux commercial seamonkey build 2000-091408-m18 installed on P200 RedHat 6.2 macos commercial seamonkey build 2000-091504-m18 installed on G3/400 OS 9.04 Overview Description: Found a corner case for bug 23637. If you edit your prefs.js file and remove the destination value for your draft and template, you create a condition where you receive a bogus error dialog. For example, when you save a draft, you will receive the first error: "Your sent operation was successful but copying the message to your sent folder failed. Would you like to return to the compose window?" If you press ok or cancel, another error dialog will follow. "Unable to save your message as draft. Please verify that your mail preferences are correct and try again." If you press ok, you are returned to the compose window. In the Mail&News Account Setting dialog, the default location for draft/template would be null. The drop down said to choose a folder... If you close the window by clicking on the "X", then it will prompt if you want to save the draft. Clicking on the save button will bring you to the 2 dialogs. Steps to reproduce problem: 1) Edit your prefs.js file Remove the default location for draft and templates. e.g. user_pref("mail.identity.id1.draft_folder", ""); user_pref("mail.identity.id1.fcc_folder", ""); 2) Save your changes 3) Start seamonkey 4) open mail 5) Start a new message I had a rich text compose window open 6) Type in some text for the subject and something in the message body 7) Click on the save button 8) First dialog indicating that your mail message was sent and could not be copied to sent folder. 9) Click on the cancel or ok button 10) 2nd dialog appears. This dialog is correct. Actual Results: Two dialog appears. The first dialog is confusing and bogus. The second dialog is ok. Expected Results: The 2nd dialog stating that your message was not saved and to check you preferences to correct issue and try again. Additional Builds and Platforms Tested On: Additional Information: This bug is should not occur in normal operation, but if the prefs.js should ever get corrupted, this situation may occur. This problem does not occur if you had no default location for the sent folder.
Jeff, this is the bug we discussed yesterday.
sorry Peter but I don't recall. Anyway, accepting...
changing milestone to unknown. It will get changed back when we figure out what milestone to put this bug in.
WFM. When a FCC folder (or template or draft) is empty, we use the default one!
Bhuvan fixed this a while ago.