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 at the (possibly significant) expense of
CPU cycles. I'll have to run some tests to see which is more costly
based on my hardware, but thanks for the suggestion!
The only problem with this scheme is if unofficial signatures don't
have the word UNOFFICIAL in their name. So far I haven't found any
but I haven't exactly been looking either. This is also my own
personal server so if there is a problem I only have myself to blame.
I've not had an issue either with official signatures and spam. 3rd
party sigs do a far better job than the built in ones, and there's no
reason to expect base clam to deal with my spam problem...it's just
really convenient, and effective. I realize I've painted myself into
this corner by using 3rd party sigs, but I also know I'm not alone.
On that note, and I apologize for not referencing, but I recall several
times in the past where people have requested the ability to call clamd
with options to limit sig usage. Their issues were different than mine,
but that option would apparently be extremely useful, yet I can't find a
bug report/feature request. In my case, clamav-milter would need
modification as well, but it's a moot point until the daemon can handle
it. Has there been an official feature request of this type that I
haven't found, should one be created, or is this out of the scope of the
development roadmap?
/Jason
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
