Closed Bug 260855 Opened 20 years ago Closed 20 years ago

Norton Antivirus File System Realtime Protection Destroys Inbox

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 116443

People

(Reporter: lee.m.adams, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10 Build Identifier: Thunderbird version 0.8 (20040913) When using Thunderbird v0.8 (20040913) in conjunction with Norton Antivirus, with the latter having FileSystem Realtime Protection enabled, the following can occur: (1) Receive email with virus/worm such as NetSky. (2) Thunderbird updates the relevant email folder on the file system. (3) Norton Antivirus scans this write and detects the presence of a virus. (4) Norton Antivirus quarantines the file. (5) Thunderbird reports an error (sorry didn't copy the text). (6) When restart Thunderbird the entire Inbox is lost. I know a lot of people use Norton Antivirus and the error above is catastrophic (has happened to me twice) so I would imagine it needs looking at a.s.a.p. If you need any more information please email. It is obviously a bug that I am loathe to attempt to reproduce because of the nature of what causes it (viruses, worms, etc.). Reproducible: Didn't try Steps to Reproduce: 1. Oops, already did this above. 2. 3. Actual Results: Lost my whole inbox after restarting Thunderbird, presumably because Norton Antiviris intecepting the save of the email upset the application. Expected Results: Not lost my inbox! Presumably it should have reported the failure to write the email but just carried on working as normal. I suppose this could be a tricky one to fix as it may involve fundamentally examining the way in which Thunderbird writes email to the file system, but it seems a very high priority to me.
*** This bug has been marked as a duplicate of 116443 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.