It appears that Mozilla queues biff requests when a server is slow, and then once the server comes back attempts to biff several times in a row. Often that means that any other mail-related networking activity takes forever. To reproduce: 0) Connect to a server with many large folders (to make sure that each biff takes non-trivial amount of network activity). 1) Set biff to fire every minute (on all accounts) 2) Make sure that the link between you and the server is slow (e.g. use dialup) so that each biff needs more than one minute to complete. Watch that it becomes almost impossible to use MailNews (opening a folder can easily take >10 minutes or more), but it becomes tolerable if the biff is turned off. I am guessing that the problem is that biff requests take over all the existing connections to the server (make sure you have the usual limit on the number of connections to a single server). I am currently using RedHat Linux Severn Beta, Mozilla 1.4.1

Looking at nsMsgBiffManager::PerformBiff(), I don't see how this could occur. There will only be one Biff queued per server and if a server is busy, the Biff for that server won't be performed, it will just get queued for another interval.

sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.

seems like this should be WFM based on comment 1. Aleksey, do you see this in any recent releases?

(In reply to comment #3) > Aleksey, do you see this in any recent releases? My setup is way different from what I had back then - I have no way of testing it.

RESOLVED INCOMPLETE due to lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.