On 9/29/2010 6:41 PM, Ted Hatfield wrote:
I configured clamav-milter to accept on infected rather than reject on
infected.
I then created two custom spamassassin rules to score the message.
That's certainly a viable workaround which conserves memory as compared
to running a second clamd, but
I currently use clamav-milter with 3rd party sigs in sendmail and am
writing the list to see how people are handling special accounts like
abuse@ or postmas...@. clamav-milter has the ability to whitelist
e-mail accounts, but it's all or nothing. Obviously, the abuse@ address
will receive s
On 2010/09/29 3:38 PM, Chuck Swiger wrote:
Do you perform egress filtering of all of the mail traffic coming from your domain(s)? If so, then (modulo signature updates), any genuine abuse report about
mail which actually did come from you should be allowed back in.
Yes, I use clam for egress f
Hi, Jason--
On Sep 29, 2010, at 12:18 PM, Jason Bertoch wrote:
> I currently use clamav-milter with 3rd party sigs in sendmail and am writing
> the list to see how people are handling special accounts like abuse@ or
> postmas...@. clamav-milter has the ability to whitelist e-mail accounts, but
I currently use clamav-milter with 3rd party sigs in sendmail and am
writing the list to see how people are handling special accounts like
abuse@ or postmas...@. clamav-milter has the ability to whitelist
e-mail accounts, but it's all or nothing. Obviously, the abuse@ address
will receive s
