Closed Bug 472203 Opened 16 years ago Closed 16 years ago

folder retention policy "use server defaults" behaves oddly, doesn't always stick

Categories

(MailNews Core :: Backend, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mkmelin, Unassigned)

References

Details

(Whiteboard: [fixed by bug 515316?])

The folder retention policy checkbox for "use server defaults" behaves very oddly. STR (on trunk, for a new profile): 1) Create a (pop) acccount 2) Create two folders The folders do not get the "use server defaults" checked. (They get the "do not delete messages".) I think they should preferably have the "use server defaults". However, if I check the "use server defaults" for one folder, it won't always show up after restart, and sometimes both folders get the "use server defaults" after restart. Seems totally arbitrary what will happen next. I'm not sure if the setting is actually lost, or if it's some oddness when setting up the folder properties for display that makes it display the wrong thing.
This might be related to bug 472446...
I could not reproduce this. If this is related to being unable to open the folder db in folderProps.js, as in bug 472446, then you would also see the character set as Arabic, and you should also see an error console message about the failed db open. Do you see any of this?
No error in the console, and the charset stays "western".
Depends on: 499306
I've seen this as well, though it appears that useServerDefaults is properly used in folderPropsOnLoad() and folderPropsOKButton() in folderProps.js. The issue seen in bug 499303 may be related but appears to be different, both that one and the issue here may be solved in the UI-backend bug 499306.
Blocks: 326584
Nominating for blocking status per discussion in bug 464355. While the effect of flipping the preference unintentionally is benign as long as the defaults are used, I can imagine cases where dataloss occurs. This may also indicate a hidden issue in the backend that should be looked at for stability reasons.
Flags: blocking-thunderbird3?
Flags: blocking-seamonkey2?
OS: Linux → All
Hardware: x86 → All
We'll approve as blocker bug 499306, which should solve the root cause of this bug, according to bienvenu.
Flags: blocking-thunderbird3? → blocking-thunderbird3-
Does this still happen with recent nightlies?
Yes, but I'm not sure if it's the same issue or a different one after the patch for bug 499306 checked in (see bug 515316 filed today, which is however more specific and reproducible than what's described here).
(In reply to comment #0) > 1) Create a (pop) acccount > 2) Create two folders > The folders do not get the "use server defaults" checked. > (They get the "do not delete messages".) > I think they should preferably have the "use server defaults". FYI. If "Local Folders", folder creation sets "Use my account settings"(former "use server defaults") checked. And opposite request to yours is filed for "Local Folders"(bug 515037. See also bug 515316 comment #2).
It unclear to me if the backend is fixed or if there's some edge case still happening - in any case, this doesn't look like something to me that we would hold back a release for - even if a fix would surely be nice.
Flags: blocking-seamonkey2.0? → blocking-seamonkey2.0-
Magnus, this should have been fixed by bug 515316 as well, do you want to keep it open UNCO for further QA or close WFM/duplicate?
Whiteboard: [fixed by bug 515316?]
Can't reproduce anymore, so likely bug 515316 took care or if. WFM.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.