For unrelated reasons. yesterday I uninstalled avast free antivirus (using avastclear.exe) and reinstalled avast free 17.4.2294. Ever since, avast is blocking incoming email when the email shield is enabled. I have checked my firewall settings (Privatefirewall 7.0) and cannot find any rules denying access. Naturally, I do not want to keep the email shield disabled. Any help troubleshooting the problem would be greatly appreciated. My OS is Windows 8.1 Pro (64 bit).
The problem occurs with all three email clients I am using: Thunderbird, Outlook and gmail. Outgoing messages are not affected. FWIW, Thunderbird produces the following error message: "An error occurred with the POP3 mail server. Mail server pop.telus.net responded:
Thank you for your prompt reply. Unfortunately, I have tried using the Repair tool via Control Panel twice to no avail. I don’t know if it is normal but, when using Repair, the final “launch executable” step seemed to take forever (several minutes) to complete.
Thank you both for your suggestions. However, despite a clean uninstall and a fresh reinstall with the offline Avast Free AV setup program, the problem remains. However, I may have identified where the problem is occurring.
If I disable the Mail Shield, the problem disappears. However, the problem also disappears if shut down my firewall, Privatefirewall 7.0. I have double-checked to ensure that all rules relate to avast modules are set to allow traffic. Nevertheless, there appears to be some conflict between the latest version of Avast Free AV and Privatefirewall 7.0. There have been no recent updates to Privatefirewall, so the conflict would appear to have been introduced by the latest version of avast free.
Faced with the choice of disabling the Mail Shield or shutting down my firewall, there really is no choice and I obviously have to disable the Mail Shield. I don’t know if you have any further suggestions to resolve the issue.
If I understand correctly, Windows 8.1 FW only protects for incoming traffic. Arguably, protection from unwanted outgoing traffic is at least as important. e.g. should unknown malware somehow find its way onto your computer.
However, to do so on a selective basis appears to be quite complicated and would require considerable time to determine which programs need rules to allow outgoing permission. The article suggests that third party software, Windows Firewall Control, can simplify matters. There are deficiencies, e.g. it does not sync with Windows FW.
While composing this, I notice that others have posted alternative suggestion for providing outgoing protection with Window FW.Thank you all for your generous assistance. I will explore different solutions and report back when I have settled on one.
I decided to uninstall Privatefirewall 7.0 (after saving its settings should I want to return to it) and am now using Windows 8.1 Firewall, supplemented by BiniSoft’s Windows Firewall Control to manage outgoing traffic. I am happy to report than I am no longer experiencing any problems with Avast’s Mail Shield.
Once again, thank you everyone who kindly offered suggestions and assistance.
Glad you got sorted. Really one of those configuration issues brought into play by changes avast has had to make to keep up with advancing and more complex malware threats, and related software user configurations, security or otherwise, that avast is then not able to completely test for all of them.
I use PFW, too (on w7, though, not w8). It worked with avast v17.4 without problems. But I downgraded avast for other reasons. And I would never ever ditch any of my software for a bug of another software (in this case avast).
I really get annoyed by this sentiment that if (a new version of) avast is having problems it’s always the other software’s fault. It’s almost never avast’s fault - god forbid!
If the only thing that changed on a system is the version of avast it’s avast’s fault. Period.
where to find older setup version? i checked on mom’s laptop and her version is 17.3.2291, mine which is screwed for not loading UI is this famous 17.4.2294