Closed
Bug 40692
Opened 25 years ago
Closed 17 years ago
Multiple Unsent Messages folder, only one pop account works with Send Unsent Messages / send later [after profile migration from NS4]
Categories
(MailNews Core :: Profile Migration, defect)
MailNews Core
Profile Migration
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: esther, Unassigned)
References
Details
Using build 2000-05-25, if user has multiple POP accounts they will have
multiple Unsent Message folders, but only one works with the Send Unsent
Messages menu item (the one under Local Folders). There are two ways users can
have multiples of these folders, through migrating a POP account and with the
creation of each pop account we create one.
Changing from critical to major, my mistake
Severity: critical → major
Comment 2•25 years ago
|
||
to reduce (but not eliminate this problem) we should not create so many "Unsent
Messages" folders.
worst case scenarios:
1) a pop user in 4.x migrates with messages in their unsent messages folder.
when the user hit "send usent", those old messages would not get sent.
2) a user manually puts messages into the wrong unsent messages folders, and
they don't get sent.
not a beta stopper. marking m20.
Status: NEW → ASSIGNED
Summary: Multiple Unsent Messages folder, only one works with Send Unsent Messages menu item. → Multiple Unsent Messages folder, only one works with Send Unsent Messages menu item.
Target Milestone: --- → M20
QA Contact: esther → sheelar
Comment 3•23 years ago
|
||
*** Bug 100857 has been marked as a duplicate of this bug. ***
Comment 4•23 years ago
|
||
nominating this for the next release.
This bug has been there for a while in many of our releases. I see that many pop
users who are migrating their account are having problems with multiple unsent
message folder. See comments in bug 104443, and bug 100857.
Keywords: nsbeta1
Updated•23 years ago
|
Updated•23 years ago
|
Since this bug caused by Profile Migration, change component-->Profile Migration
Component: Composition → Profile Migration
Comment 6•22 years ago
|
||
I am using Build 2003050714 and I have the same problem. Furthermore, in Edit /
Properties... / Copies & Folders, the combo after the "Sent" Folder on: radio
button stays empty, and the radio button always reverts to the "Other" value. I
have 4 different mail accounts on 3 different ISPs, and I don't think this
problem is only migration-related.
Updated•20 years ago
|
Product: MailNews → Core
Summary: Multiple Unsent Messages folder, only one works with Send Unsent Messages menu item. → Multiple Unsent Messages folder, only one works with Send Unsent Messages menu item [after profile migration from NS4]
*** Bug 124449 has been marked as a duplicate of this bug. ***
*** Bug 155439 has been marked as a duplicate of this bug. ***
Comment 10•19 years ago
|
||
many bugs duped to this one receive the error message (among other messages)
Unable to save your message
are Bug 253370 and Bug 301859 caused by this bug?
is bug 155439 comment 10 a work around?
[unfortunately this component, profile migration, has no owner or QA - but perhaps someone will pick up the ball]
Assignee: sspitzer → nobody
Status: ASSIGNED → NEW
Keywords: helpwanted
QA Contact: stephend
Summary: Multiple Unsent Messages folder, only one works with Send Unsent Messages menu item [after profile migration from NS4] → Multiple Unsent Messages folder, only one pop account works with Send Unsent Messages / send later [after profile migration from NS4]
Comment 11•19 years ago
|
||
*** Bug 301859 has been marked as a duplicate of this bug. ***
Comment 12•19 years ago
|
||
*** Bug 253370 has been marked as a duplicate of this bug. ***
Comment 14•17 years ago
|
||
->WONTFIX since 4.x migration has been dropped on trunk.
Though if someone puts together a safe 1.8 branch only patch, why not...
Status: NEW → RESOLVED
Closed: 17 years ago
Keywords: helpwanted
Priority: P3 → --
QA Contact: profile-migration
Resolution: --- → WONTFIX
Target Milestone: mozilla1.2alpha → ---
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•