Closed
Bug 233058
Opened 21 years ago
Closed 20 years ago
special IMAP folders like "#public/" loose their configuration on every new startup.
Categories
(MailNews Core :: Networking: IMAP, defect)
MailNews Core
Networking: IMAP
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 239868
People
(Reporter: mail, Assigned: Bienvenu)
Details
User-Agent: Build Identifier: Mozilla Thunderbird 0.5a (20040129) and also the Mozilla Mail Client of 1.4-1.6 On every new startup, the special IMAP folders like #public are loosing their individual configuration. This means that if I am going to set the display order of a folder within the #public tree, exit ThunderBird or Mozilla and start it again the order is reseted to the default of Thunderbird instead of keeping the last set order. Reproducible: Always Steps to Reproduce: 1. Start ThunderBird or Mozilla and try to connect to a special folder within the "#public" IMAP tree. 2. Try to set the mail display order of a folder within this tree. 3. Restart ThunderBird or Mozilla and check if it still has your individual order set or if it was reset to the default again. Actual Results: The order of the mail display was set to the default instead of displaying the order that was set in the session before the restart. Expected Results: The order of the mails should have been like in the previous session. Another curiousity is, that as soon as the Mail client starts up and tries to initialize it's IMAP folders, it also displays the subscribed folders in the #public tree, but within a few seconds replace them by totally new copies. This somehow looks like the client can't identify the previously used configuration and restores it with a default setting.
After checking with the latest nightly build of Thunderbird (20040412) this bug seems to be fixed somehow now. All #public folders keep their configuration now on startup. So I guess some changes along the way also fixed that problem.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Comment 2•20 years ago
|
||
Saying "fixed somehow" means it should be resolved as WORKSFORME.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Updated•20 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Comment 3•20 years ago
|
||
yes, this is actually a dup of a bug 239868
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Assignee | ||
Comment 4•20 years ago
|
||
*** This bug has been marked as a duplicate of 239868 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: MailNews → Core
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
•