I use avast since several months. Yesterday, i’ve updated Mozilla Thunderbird to the new version 2.0. But now, i have an issue between this 2 programs:
Thunderbird receive an new mail. While thunderbird downloads this mail, avast scans it for viruses. But this scan let thunderbird think, that the mail is already read. So i receive new mails, but they are never marked as new. If i turn off the mail scanner in avast, all works like it should.
I have been using Thunderbird 2 beta2, RC1 and now the production release of Thunderbird 2 with avast. I have never seen this problem with any of my accounts in Thunderbird.
Can you give us a little more information:
Your operating system
The release of avast you are using
Is this a regular POP email account (from your ISP) using port 110 for the POP connection?
Are you running any spam filtering software on your system?
Do you run any filters in Thunderbird on your incoming mail messages?
I’m using the latest release of avast (updated on thursday). As operating system i use Windows XP SP2 without any SPAM-software. In thunderbird, i don’t use any filters. I connect to my isp using the IMAP-Protocol…
I have just conducted some tests on two side by side machines, both are up to date XP SP2 machines. Both are using the latest avast update. One machine is using TB2 and one is using TB 1.5.0.10.
I have a number of messages sitting in my IMAP account, some have read status (because I read them via the Web interface of the account) and some are unread.
When I connect to the IMAP account from either machine the same status for each message (as it appears in the Web interface) of read or unread shows up in TB2 and in TB 1.5.0.10.
I have noted a few reports in the Thunderbird Support forum reporting instances where IMAP accounts are showing new messages with a status of read after the upgrade to TB2 but there have been no explanations in those threads so far.
can you give a little more information about the problem identified?
Is it specific to the latest release of avast?
Is it specific to any particular mail client?
Since increasing numbers of Thunderbird IMAP users are reporting this in the Thunderbird forum should they be asked if they are also avast users? (The most recent releases of avast came out about the same time as the Tunderbird 2 release).
It is not specific to the latest avast release. It depends on behavior of both mail client and server. It started to appear with Thunderbird 2 because they changed handling IMAP connections a little bit, but it appears only with some IMAP servers.
It is very likely that users reporting this problem have avast.