On 12/3/2012 8:21 PM, /dev/rob0 wrote: > On Mon, Dec 03, 2012 at 07:34:13PM -0600, Stan Hoeppner wrote: >> On 12/3/2012 2:55 PM, mouss wrote: >>> Le 03/12/2012 10:07, Stan Hoeppner a écrit : >>>> You might want to look into these as well: >>>> >>>> -o content_filter= >>> ahem? submission or not, it must go through a malware filter. >> >> Sorry for the oversight. Yes, one would want to include clamav or >> other malware checker, but exclude Spamassassin or any spam filter >> geared toward inbound public mail. Excluding SA reduces load, and >> prevents mail being scored as spam due to dynamic IP status, etc. > > Spamassassin can be tailored for the job of submission scanning. The > URIBL checks are particularly good at detecting compromised accounts.
I specifically avoided mentioning this scenario in hopes of preventing a long OT thread about SA implementation. It seems clear that outbound scanning wasn't on the OP's radar. If he chooses to implement it at a later date it could be picked up in discussion at that time. -- Stan
