Closed Bug 225430 Opened 21 years ago Closed 20 years ago

Unable to save settings to save my drafts and templates

Categories

(SeaMonkey :: MailNews: Account Configuration, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 221386

People

(Reporter: zzett, Assigned: sspitzer)

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; de-AT; rv:1.5) Gecko/20031007 Build Identifier: Mozilla/5.0 (Windows; U; Win98; de-AT; rv:1.5) Gecko/20031007 If i want to save my account-settings to save ny draft or templates to the folders and then press the OK button.It does not work.The settings can not be saved. Reproducible: Always Steps to Reproduce: 1.I am going to Edit and then to Account settings. 2.Then i am goind to Copies + Folders. 3.I am pressing the button to: Place a copy in Sent Folder on my account. I am pressing the button to: Keep a message in Drafts Folder on my account. I am pressing the button to: Keep a message in Templates Folder on my account. Finally i press the OK button. Actual Results: Settings in Copies + Folders disappear.(Can't be saved) Expected Results: Let the user to be able to save their settings propperly
I know how to fix this one! The problem is that the path to the templates folder is messed-up. In my case, it was because the slashes are reversed since I used the same Mozilla profile on Linux and Windows. Open your prefs.js file, and find the line that looks something like: user_pref("mail.identity.id1.stationery_folder", "mailbox://youremail@your.isp.net\\Templates"); There is a nearly identical entry for the Drafts and Sent folders. Manually fix those lines to read: user_pref("mail.identity.id1.stationery_folder", "mailbox://youremail@your.isp.net/Templates"); Your problem may differ slightly, but I expect it comes down to a corrupted line in the config file. In my opinion, this is still a bug, because if the user changes the setting in the GUI, Mozilla should rewrite the line and fix the problem. There should be no need to change the prefs.js file manually. A bonus would be to make the prefs.js file parser handle slashes in either direction, or to fix them when it rewrites it.
Sven Heise, did comment 1 help you with your problem? Please read bug 221386, and mark this bug as a dupe of that if you think that is appropriate; if not, please say why.
No response from reporter, duping. *** This bug has been marked as a duplicate of 221386 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.