Avast Email and Outlook protections block my Outbox

Hi,
Just want to know if someone else have the same problem as mine. When I try to send emails from Outlook, they stick in my outbox and got and error msg like: “Sending’ report error (8x00CCC80)…”. The Outlook support center identify the cause from my anti-virus software, which is Avast 4.8.1368 and suggest to desactivate it. So I have desactivated the Outlook and Email protections. The result is that now I can send again my emails. Is this because of a newer version of an Avast viral DB? Forcing this signify that now I don’t have any Outlook protection. Can anybody can help with this?

Regards

Hi Mbaz, welcome to the forum.
It’s usually down to one of three reasons:

  • Remnants of a prior AV program. What was your last AV, and how was it uninstalled?
  • Firewall is blocking it. common with ZA and OA, so I’ve read. What is your firewall?
  • Mail settings not set up correctly in Avast. (Default usually works.)

Welcome Mbaz

avast! has good file protection so anything on your system can not leave on emails.

Having the notification that the email is virus free is not necessary IMHO.

The problem is that SSL settings have to be absolutely correct and if your ISP is using SSL to send email then you need to install Stunnel:
http://www.stunnel.org

@ Mbaz
Can you post the full text of the error message, not just that extract as that may help pin down the problem, thanks.

You don’t say what version of MS Outlook (not express) that you are using ?
It is possible that the avast plug-in within Outlook is disabled (as the avast plug-in within avast would mean you should be able to send even to SSL connections), so check that it isn’t disabled:
Outlook 2007 > Tools > Trust center > Add-ins > Manage Disabled items.
Outlook 2003 > Help > About > Disabled items
Outlook 2000 > Tools menu > Options > Other > Advanced Options > Add-In Manager.

Hi DavidR,
My Outlook version is 2007 (12.0.6514.5000) SP2.0 MSO (12.0.6425.1000). I have set to Disable : Outlook 2007 > Tools > Trust center > Add-ins > Manage Disabled items. This does not solve the problem.

No you shouldn’t be setting it to disable, doing that would most certainly through a spanner in the works, the plug-in needs to be running.