Closed Bug 243573 Opened 21 years ago Closed 20 years ago

Profile in mail (copies and folders) loses focus: no longer allows "sent mail" to be saved

Categories

(MailNews Core :: Composition, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 221386

People

(Reporter: ian42, Assigned: sspitzer)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 Without any warning, the profile changes such that sent mail is no longer saved to the "sent" folder. When I go out to the profiles and change them appropriately, and indicate "OK", the changes are shown, but if I log out or simply reopen the mail profiles (copies and folders) the changes made did not "stick." It is important that I keep copies of sent mail! Reproducible: Always Steps to Reproduce: 1. Check that sent mail was saved to "sent" folder. If not then: 2. Open "Mail and Newsgroup Account settings" 3. Check to see that "Sent" is checked and to the right location 4. If not, then check appropriate box(es) and select OK Actual Results: Changes did not stick. It was as if I never did anything. Cannot change folders setting Expected Results: Held changes so that sent mail would be saved in {username}/Sent
it would be helpful if you included things like path info. does your computer have a d: drive or something like it? (you could attach your prefs.js, ... read it before posting to verify that nothing sensitive is bleeding, you can names to something like 'censored' if you care...).
Marking this as the duplicate I think it likely is. Ian Robertson, if you feel that this duplicate is in error, feel free to reopen this bug, but please provide information as to why you think it's different. *** This bug has been marked as a duplicate of 221386 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.