Closed
Bug 18260
Opened 25 years ago
Closed 25 years ago
Send Later/Send Unsent fails if no local mail (profile is all POP)
Categories
(MailNews Core :: Backend, defect, P1)
MailNews Core
Backend
Tracking
(Not tracked)
VERIFIED
FIXED
M13
People
(Reporter: laurel, Assigned: sspitzer)
Details
Send later fails when there is no "local mail" folder hierarchy, always tries to save to a local mail Unsent Messages folder. 1. Set up a new profile with only POP account(s). (Because of the fix for bug #18064, we no longer create local mail folders if there is no IMAP account.) 2. Open and login to POP inbox, provide proper password. 3. Compose a new message and File|Send Later. Result: send fails, alert appears "StringID(hex)=8000ffff", click OK to alert, composition window still open. Message is not sent or stored in Unsent folder. Expected: Composition window should close and message should be stored in Unsent Folder under account server folder hierarchy. Note: If an IMAP account is added so that there is a local mail hierarchy, the same POP account will be able to send later, but the unsent message will be stored in the local mail folders' Unsent Messages. Found using 1999-11-08-09m11 commercial build NT 4.0
Summary: Send Later fails if no local mail (profile is all POP) → Send Later/Send Unsent fails if no local mail (profile is all POP)
Also fails on migrated POP profile (migrated in nov8 build). Profile migrated existing local mail Unsent Messages and its contents to Unsent Messages under server folder hierarchy. Even though the messages are displayed in the migrated unsent folder, doing Send Unsent Messages doesn't work in the 5.0 profile, because we're not looking in the right place for the unsent message folder.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M12
Assignee | ||
Comment 2•25 years ago
|
||
accepting. yes, the problem is I hard coded the unsent messages URI to be "nobody@Local Mail/Unsent Messages" or something. should be easy to fix. I need to fix that. nice catch, laurel. marking m12.
Assignee | ||
Comment 3•25 years ago
|
||
working on the fix now. here's a work around: set the "mail.default_sendlater_uri" pref to besomething like"mailbox://sspitzer@tintin/Unsent Messages" where sspitzer is the username, tintin is the pop server, and Unsent Messages is the folder for Send Later messages. I'm working on the fix so that when you migrate a pop account, this pref gets set automatically.
Assignee | ||
Updated•25 years ago
|
Whiteboard: seeking checkin approval
Assignee | ||
Comment 4•25 years ago
|
||
fix in hand and code reviewed. awaiting approval.
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 5•25 years ago
|
||
fix checked in. now, when you migrate, the pref will get set correctly for pop. I'm working on a related bug right now. if the pref is not set correctly, or if it is set to a non-existant folder, we aren't getting the right error message. we're getting "StringID(hex)=8000ffff" I'll open a new bug on that.
Assignee | ||
Comment 6•25 years ago
|
||
see #18383 for the bug on the bogus alert.
Comment 7•25 years ago
|
||
Release Note for M11
Using builds 1999112209m12 on win98 and linux and build 1999112208m12 on mac this is partially fixed. Not fixed: 1. A newly created POP only profile is still broken. Can't send to the Unsent Messages folder. Fixed: 1. A migrated POP only profile w/messages in Unsent Messages folder works correctly. New messages were delivered in that folder and all (existing and newly sent messages to that folder were sent when clicking "Send Unsent Messages". Better but not completely fixed: 1. The alert is no longer a bogus alert, but the new text wrongly states "Unable to save your message in order to send it later. Please verify that your mail preferences are correct and try again." There is no preference setting for directing the Unsent messages to a folder and I don't believe one is in the spec. If this error message is referring to the Sent folder, I had that set corrrectly in Account Setup not Preferences. Currently there is no way a POP only account can send later unless the user edits the prefs.js file. Reopening, since the original steps for this bug are not fixed.
Updated•25 years ago
|
Target Milestone: M12 → M13
Assignee | ||
Updated•25 years ago
|
Status: REOPENED → ASSIGNED
Priority: P3 → P1
Assignee | ||
Comment 9•25 years ago
|
||
moving to p1. and accepting.
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 10•25 years ago
|
||
fixed, now that we always have a "local folders" account laurel brings up a good point about the error message. I tell the user "send later" fails because the pref may be bogus, but there is no ui to fix it, and we don't want them in there hacking. what to do? perhaps that should be a new bug / or an issue for the issues meeting. knock on wood, that error and that alert shouldn't happen because we always have the "Local folders" account.
Comment 11•25 years ago
|
||
Cant't test this until I get an M13 build that doesn't crash when creating a new mail account. 2/13/00
Comment 12•25 years ago
|
||
Using build 2000-02-07-09M14 on wi98 and 2000-02-07-08M14 on mac and linux this is fixed. As stated by sspitzer, we now get a Local Folders account (w/Unsent Messages folder) when creating a New Profile with a POP account. Verified
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
Comment hidden (collapsed) |
You need to log in
before you can comment on or make changes to this bug.
Description
•