User-Agent: Mozilla/5.0 (compatible; Konqueror/3.2; Linux) (KHTML, like Gecko) Build Identifier: version 0.8 (20040913) I use Thunderbird 0.8 on Linux (RH9-derivative). I am using an IMAP server for local storage (DbMail). When Thunderbird opens a big IMAP folder that it did not open before, it downloads the headers for all the messages in it - as it should do; it counts them when downloading. Then, it says "Downloading Message" in the status line, and starts a long downloading process. According to the IMAP server's log, it downloads the bodies of all the messages in the IMAP folder. Apparently it does not save these bodies anywhere; when I later open a message in the folder, Thunderbird downloads its body again. (This folder is not "selected for offline use" - I did check this). Reproducible: Always Steps to Reproduce: 1. Use an IMAP server that logs every IMAP command. I use DbMail 2.0 (http://www.dbmail.org). 2. Create an IMAP private folder with 10,000 or more messages, without using Thunderbird. (I used DbMail's mbox import script; using another email client will probably be as good). 3. Register this IMAP account in Thunderbird. 4. Click on that folder in the mail tree. (it should not be "selected for offline use".) 5. Wait for the "Downloading headers" count to complete, and see what comes next Actual Results: Displayed "Downloading message" and spent a long time communicating with the IMAP server. According to the IMAP server log, it requested the body of every message: COMMAND: [6615 UID fetch 108434 (UID RFC822.SIZE BODY.PEEK)] and this for every mesage in the folder. Expected Results: It should have downloaded just one message body for the current preview pane.
it's analyzing the unread messages that it has not seen before for junk status - you'd need to turn off the junk mail controls for it not to do that. There are requests to be able to specify folders *not* to check for spam when you open them...
Status: UNCONFIRMED → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.