I just updated to Avast Home 4.7.844 this evening. No error messages occurred during/after install. After turning off machine and coming back later, booting up rendered four Mail Scanner error messages as follows:
Avast will not be able to protect incoming mail (IMAP Protocol) Error 10022
Avast will not be able to protect outbound mail (SMTP Protocol) Error 10022
Avast will not be able to protect News (NNTP Protocol) Error 10022
Avast will not be able to protect Pop3Mail (Error 10022)
If I left click the a ball in sys tray, it says the provider is running, but when I mouse over the a ball, it is not included in the “total running count”. I went on-line and did the repair via Control Panel but the problem persists. Any suggestions?
FYI: My System Hardware/Software:
Dell Dimension 4700 Desktop Intel Pentium4 2.80 GHz
512MB DDR2 SDRAM
160GB Serial ATI Hard Drive - NTFS
17" Flat Panel E173FP Monitor
Radeon X300 Video Card
128 MB PCI Express x 16
48x SONY CRXX216E CD-RW drive
Dell 922 AIO Photo Printer/Copier/Scanner
SBC DSL 2 Wire Home Portal External Modem w/built-in hardwire firewall
Windows XP SP2 V5.1.2600 with Internet Explorer v6.0.2900
SBC Yahoo DSL Browser (modified IE)
Yahoo mail only
Java JRE v1.5.0 (build 1.5.0_06-b05)
FlashPlayer 8
SpywareBlaster v3.5.1
SpywareGuard v2.2.0
Spybot Search & Destroy 1.4 (Teatimer off)
IE-Spyad
Ewido 3.5 Free (EwidoGuard removed)
Adaware SE 1.06r1 (on demand)
CCleaner v1.29.295
MVPS Hosts File
McAfee Personal Firewall Plus v7.1.113 (WinXP Firewall OFF!)
Avast!4.7 Free Home Edition Build: 4.7.827
Roxio PhotoSuite 5.0.149.0
MS Windows Defender Beta 2 v. 1.1.1347
Your personal firewall has probably blocked up the mail scanner (ashMaiSv.exe) when the file changed after the update. You need to reassign permissions to it.
vojtech,
was the mail scanner the only component to change in this update? If not, strange that a firewall would choose to block it only.
This type of error occurs only in proxies that listen on some port, i.e. the Mail Scanner and the Web Shield.
Thank you both for your input & quick responses. Vojtech, I just checked FW permissions. Sometime in the last month I changed avast access to “Outbound Access Only” in my MFW. But after doing so, I encountered no avast problems, so figured all was OK & they only needed outbound access to function properly. The update, apparently, does not like that FW status, though. I just changed access to “Full Access” & error messages are not recurring this morning, after three reboots. So I think you were right.
??? But answer me this question. Do Mail, Standard, Network & Web Shields (I only run these 4) all absolutely have to have “Full Access”? Because my mail scanner (in fact all 4 providers) worked properly after the change to “Outbound Access Only”. Would have thought these errors would have come up right after the FW changes were made. The update clearly triggered off these errors. Curious, don’t you think? ??? Do only ashmaiSv.exe & ashwebSv.exe need “Full Access”. I like to keep the full access programs to a minimum on my pc.
Sorry Alanrf, I forgot to answer your question. Yes, the mail scanner was the only component to have problems after the program update.
The ashMaiSv.exe and ashWebSv.exe need to accept connections (like a server, but only from within your computer), that’s probably what they mean by “Full Access”. This requirement is not new in this update. Other avast components need only outbound access.
Yes, Vojtech, “Full Access” in McAfee PFW means server access (inbound & outbound). That’s was the precise clarification I was looking for. Thank you sooooo much for your reply. I have now set my firewall permissions as you have indicated.