Closed Bug 21191 Opened 20 years ago Closed 17 years ago
Duplicate sendlater alert dialog if mail
.default _sendlater _uri set to bogus folder
Using 12-08-08m12 commercial build mac OS 8.5.1 and Linux 6.0 (haven't yet tried with current windows build -- having problems with it) Found while verifying bug #18383. The alert which displays when using send later when default_sendlater_uri is pointing to a nonexistent Unsent folder location is displaying twice. 1. Use a POP account in a profile having no IMAP, no local mail folder. 2. Change prefs.js "mail.default_sendlater_uri" pref value to "mailbox://nobody@Local Mail/Unsent Messages" 3. Launch 5.0 to messenger. 4. Open the POP account. Compose a new message and Send Later. 5. An alert displays reading: "Unable to save your message in order to send it later. Please verify that your Mail preferences are correct and try again." Click OK. Result: alert dialog displays again and must be OK'd again to dismiss. Expected result: alert dialog need only display once.
20 years ago
Status: NEW → ASSIGNED
Target Milestone: M16
two alert dialog is not good, but nothing we can't live with for a while, seeing as they get this in an error case. movnig to m16. accepting. good catch, as always, laurel. adding rhp to the cc list.
Mass moving M16 to M17 - look for nsbeta2 before anything else.
Target Milestone: M16 → M17
moving to future milestone. Does this bug still exist?
Target Milestone: M17 → Future
Laurel, I will repeat putterman's previous and 7 months old question: does this bug still exist?
We'll look at it when we get a chance from testing the trunk builds and from writing/updating our test specs. This bug is already marked future regardless if it exists or not, so we'll look at it when our schedule allows us to.
worksforme moz 2003032416/win98
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Summary: Duplicate sendlater alert dialog. → Duplicate sendlater alert dialog if mail.default_sendlater_uri set to bogus folder
You need to log in before you can comment on or make changes to this bug.