Comments
 
posted on June 22nd 2012, at 16:00
by lunarg
We updated Avast to the latest version on a client's server running SBS 2011. The update apparently included antispam. All of a sudden, the Transport service kept failing, and all messages (in both directions) landed in the Poison Queue. Restarting the Transport service did not fix the issue, and there was nothing we could do.

Googling around, we found that the trouble was indeed related with Avast. Disabling the Antispam Shield did not resolve the issue, but disabling the transport agent in Exchange, via Powershell was the fix:

disable-transportagent "avast antispam for exchange"

After disabling the agent, everything came to life again.

@ Avast: you should really start  ...
Add a new comment
 
Your name:
Your e-mail:
Your comment:
 
Basic BBcode is supported.
Captcha:
Type the letters and numbers as shown.
/get/captcha/1618101869
Not readable? Get another.