Closed Bug 216831 Opened 21 years ago Closed 21 years ago

Unable to set Sent Mail folder preference

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 221386

People

(Reporter: meniscus, Assigned: sspitzer)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030820 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030820 For the last several nightlies, I am unable to set a preference for Sent Mail behavior. Regardless of whether I try to save a copy of outgoing mail to the Sent folder associated with the account, a different folder, or via the .bcc command, the preference is not saved, and Mozilla is not saving any copies of outgoing mail. Reproducible: Always Steps to Reproduce: 1. Choose an account (in my case a POP account) and View Settings for This Account. 2. Click "Copies and Folders", then select "Place a copy in:", and select either option ("Sent folder" or ""other"). 3. CLick the OK button. 4. Send an email. 5. Notice that a copy was not saved to the Sent folder or other location that you supplied. 6. Repeat steps 1 and 2 above; notice that none of the options are enabled. Actual Results: Preference not saved, and copy of outgoing message not saved either. Expected Results: Copy of outgoing message should be saved in the "Sent" folder or wherever you specified. I have tried deleting the old Mozilla folder and reinstalling, and I have also tried using a clean, brand new profile, to no avail (not to mention that this "make a new profile" approach is expecting waaaaaay too much of the average person who does not have 3+ hours to spend manually editing prefs files and copying Inbox data around...)
Duping to a newer bug which has trouble-shooting information. *** This bug has been marked as a duplicate of 221386 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.