Using Nov15th trunk commercial build If you make subscription changes to more than one news server (may also apply to IMAP, I haven't tried that) in one subscribe session, only the subscription changes to the last server will be retained and reflected in folder pane. 1. Profile has two news accounts, news.mozilla.org and "news". Both servers have previously been accessed in subscribe and have had their newsgroups lists retrieved. 2. From mail window, File|Subscribe. 3. Switch dropdown in subscribe to news.mozilla.org and subscribe to a couple newsgroups. Do not close subscribe dialog. 4. Switch dropdown in subcribe to "news" server and subscribe to a couple groups on that server, too. 5. OK the subscribe dialog. Check the folder pane for both news servers, newly subscribed groups show up for "news" but not news.mozilla.org. Collapse and expand both server/account levels, just to make sure, but only new subscriptions on the last server reflect in the folder pane. Result: Subscription changes to more than one news server in a single subscribe session retains only changes for the last server accessed. Expected: Any subscription changes in a given subscribe dialog session should be retained upon OK.
nominating for fix in 6.5
QA Contact: esther → laurel
I discovered later that the groups subscribed for the first server are (later?) added to the folder pane listing for the second server. So I've got groups listed in the folder pane under the second server which are invalid groups for that second server -- they belond with the first server.
great catch, laurel. this is bad. I've got a fix for this in my tree, I'll land it once I land the massive subscribe performance fix that is also in my tree. I hope to land this week.
Status: NEW → ASSIGNED
Whiteboard: fix in hand
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
OK using nov 28 commerical trunk build, linux rh6.0, win98, mac OS 9.0
Status: RESOLVED → VERIFIED
Component: MailNews: Subscribe → MailNews: Message Display
QA Contact: laurel → search
You need to log in before you can comment on or make changes to this bug.