Closed Bug 155814 Opened 23 years ago Closed 23 years ago

Norton Antivirus 2002 conflicts

Categories

(MailNews Core :: Networking: POP, defect)

x86
Windows 2000
defect
Not set
major

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: araque, Assigned: naving)

Details

When Norton Antivirus 2002 is installed, and the "scan incoming messsages" option is set, Get Messages hangs. It really does nothing. I have verified (indirectly) that there are messages waiting in the POP server. I tried an Outlook client, which errored out with some weird message from windows, but Mozilla gives no warning at all, it doesn't even timeout. When I hit the STOP button, the popstate file is updated. When I set environment variables to trace the POP activity, the log file is created but nothing ever gets written to it. The Norton Antivirus taskbar showed the Norton Antivirus icon docked, but when I double clicked it nothing happened, which lead me to suspect that there was a conflict between Mozilla and Norton. Finally, when I de-installed Norton Mozilla started working again. And if I re-install it, it will stop working.
I have norton 2002 running at work on a win98 machine with email scanning enable and have not had any problems. Reporter, what build-id are you using? Also, with some of norton's email scanning, yo uneed to specify a weird setup using your own computer as your pop server. You should ensure that you are not running and firewall program that is preventing this activity, and that Norton is set up correctly to accept Mozilla's connection (it doesn't recognize Mozilla by default)
Resolving as we have had no reply from reporter. Reporter, if you are still having this issue in a current build, please reopen and comment with details. Invalid as the original report is missing basic info.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
vrfy invalid since there is no reponse from the original reporter
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.