Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: blairjac on February 21, 2005, 04:50:16 AM
-
Hello
First I'd like to say thanks to Avast! for the nice software.
Second I'd like help resolving an issue with the mail scanner service.
After updating from 4.5 to 4.6 today, I must (manually) restart the "avast mail scanner" service from the windows xp pro sp2 administrative tools... after each reboot.
I am using Thunderbird but mail is not scanned when using OE either...
After boot up, xp claims the service is running but mail is not scanned. Ingoing or outgoing.
After restarting the service manually, the mail scanner works great!
If I roll my system back to version 4.5, everything works as it should.
Any Ideas? Thanks.
-
I am using Thunderbird but mail is not scanned when using OE either...
Is there the line 'X-Antivirus: avast!...' in the message headers, when mails are not scanned ?
After boot up, xp claims the service is running but mail is not scanned.
What is the startup type of the service - manual or automatic ?
What is the status of 'Internet Mail' provider in the avast On-access scanner window after reboot ?
Are there any error entries in the log file Avast4\DATA\log\aswMaiSv.log after reboot ?
-
How do I roll back to 4.5 I am having trouble with the 4.6 mail scanning also The 4.5 was ok with me everything was working fine
-
trouble:
I was able to roll back to 4.5 by using xp's "system restore".
vojtech:
No, there were no avast headers in incoming or outgoing mail.
(the mail scanner "tray icon" did not show up either)
Type of startup for the scanner service was set to "automatic".
Internet mail provider status was ok, terminating and restarting the provider had no effect. Only manually restarting the service via XP worked.
I have resolved the issue by using the avastCleaner.exe to uninstall, then doing a clean install of most recent avast version. Apparently, the trouble had to do with the "update" procedure. All is well now.
I did not check the log, sorry. Too late now. :-)
Thank you for taking the time to reply.