Avast WEBforum
Other => General Topics => Topic started by: tbird on September 10, 2007, 03:26:17 PM
-
Using Thunderbird and since the update I have gotten the error message 10049
avast will not be able to protect incoming mail (POP3 protocol)
I use Comodo and it is checked to allow avast mail. I sent myself some test emails and it doesn't show the incoming mail as scanned.
Any help would be appreciated.
-
This is usually an indication of the presence of another AV.
Have (or did) you another AV installed in this system, if so what was it and how did you get rid of it ?
What other security based software do you have that might monitor emails ?
-
I have used avast for well over a year and doubt that it would be a conflict with previous av. I don't know if Spy Sweeper has anything to do with email but that is the only thing running with resident protection.
-
It's working again. I went into my firewall (Comodo) and removed the web mail. Rebooted and I didn't get the error message and my firewall popped up to allow avast. Seems to have solved the problem. Thanks for your time.
-
Your welcome, that is handy, my next step below was a little more hassle.
I did a forum search for the error number and there are many hits for it, but this one (a marathon 6 pages) was also related to Comodo firewall, http://forum.avast.com/index.php?topic=27569.msg225558#msg225558 (http://forum.avast.com/index.php?topic=27569.msg225558#msg225558).
Although this one also had other complications, Norton, etc. finally reinstalling the comodo firewall resolved the problem, hopefully that may to resolve your problem. I would suggest you check for and download the latest version of comodo firewall and use that for the reinstall (uninstall, boot, install).
-
This error just happened again after I did the MS updates. Does anyone know why MS would effect this. Almost hate going to the update page.
-
I would have though that it wouldn't have had an effect, as there would be no direct change of ashMaiSv.exe, that should be the only reason comodo might block and it should first challenge for any change.
So it is more likely to be a coincidence that this happened after windows update and this is the same issue (problem with comodo blocking) as before, so take the same action as before.
-
Does anyone know why MS would effect this.
Like David said, it shouldn't be happening.
But I have a problem with Comodo and the update function of RogueRemover from http://www.malwarebytes.org/rogueremover.php and I can't see why Comodo is not allowing it to update. Sometimes, Comodo acts weird... the entries are there, allowed to connect...
-
I use Avast! 4 Home Edition and I was having a similar problem. When I started my computer I got Error 10049 and the protection for NNTP, STPM, POP etc., were inactive. I use Comodo as my firewall. I put in the trusted Trusted Applications area the following .EXE files:
avast.setup
avastXXX.setup (where XX are some numbers)
aswUpdSv.exe
ashServ.exe
ashWebSv.exe
ashMaiSv.exe
This solved my problem ;D
Kirki
-
avastXXX.setup (where XX are some numbers)
This is a strange one on me, I haven't seen it before it may have been a duplicate running so it may have had two instances of avast.setup running and that could cause strange effects like hanging the update process.
-
that happens if install fails and the file is in memory or on drive so new instance appear ...
it's rare but happens ...