Open Bug 268351 Opened 21 years ago Updated 3 years ago

invalid "check folders" message upon server change

Categories

(MailNews Core :: Account Manager, defect)

defect

Tracking

(Not tracked)

People

(Reporter: eyalroz1, Assigned: aceman)

Details

I have a POP3 server configured to use the global folders. When I change the server name in the account settings, it tells me: "The server name setting has changed. Please verify that any folders used by filters exist on the new server." But it's not IMAP... also, I don't get the same message when changing the name of my other POP3 server, which is not configured to use the global folders.
Product: Browser → Seamonkey
Assignee: sspitzer → mail
The culprit code is: http://lxr.mozilla.org/seamonkey/source/mailnews/base/prefs/resources/content/AccountManager.js#395 395 if ( (oldHost != newHost) && (filterList != undefined) && filterList.filterCount ) 396 serverChangeText = gPrefsBundle.getString("serverNameChanged"); another condition needs to be added - && of the account not going into the global inbox.
Severity: normal → minor
Status: UNCONFIRMED → NEW
Ever confirmed: true
Or perhaps the condition to add would be something about the account not being IMAP, e.g. && (newType != "imap") (provided I am reading the code correctly. Pity I don't have the time to cvs-update my source tree and test this.
I'm not sure about this. How does it relate to the global inbox? I think you can have filters on the original account/server and also on the other account that you defer to (global inbox). Yes, changing server name of IMAP means it could be a different server and there may be other folders on it, this message makes some sense. For POP3 the list of folders does not change, if you suddenly download from a different folder. Good catch, I think limiting to IMAP (or some other criteria) makes sense.
Assignee: mail → acelists
Component: MailNews: Message Display → Account Manager
Product: SeaMonkey → MailNews Core
Severity: minor → S4
You need to log in before you can comment on or make changes to this bug.