User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.0.3705) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210 The default location of imap mail folders is in c:\document and settings\<USername>\Application data\Mozilla\etc\etc\imapmail\<mailservername> All files located in c:\document and settings\<USername>\Application data\ roam with the user as they use other workstations if you have roaming enabled. If you have a laptop and have offline mail support turned on for those folders the amount of data located in the Mozilla imapmail folder can easierly top 250Mb. This data should realy be stored in c:\document and settings\<USername>\Local Application data\Mozilla\etc\etc\imapmail\ Which doesnt roam, I've changed the location to this using the prefs.js, but it then exposes another problem, the filter file must be located in the imapmail\<mailservername> folder, and if this is in a non roaming location, your mail filters do not roam or get backed up if the workstation is toasted for some reason. A possible fix for this is to have a pref setting that simply puts all folders and .msf's in a parrallel directory to the current one but swaps "local application data" for "application data" on the path for all .msf files I'm not sure if this is a bug or and enhancement, I'd lean towards an unexpect behaviour as in testing in my organsiation, it has made a huge impact in the increased time to logon and logoff. (not that people have twigged that Mozilla is the cause yet) Reproducible: Always Steps to Reproduce: 1. 2. 3.

*** This bug has been marked as a duplicate of 123080 ***

I'd like this bug to speak to the mailnews issues only. The dupe was mostly about network cache.

this sounds more like a roaming issue. A lot of information is left out of this, but I assume these files are copied to the server and that's the slowdown? Perhaps the roaming code could just copy the filters file instead of copying the whole directory and sub-directories. You don't need the msf files either. All you need is the filters file.

This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/

This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.