Loren Wilton wrote: > > > My thought on a simple solution would be to feed the webmail into > procmail, > have it run SA. SA will do report_safe markup on spam. You can now look > at > the classification result in procmail and route the probable spam to a > special mailbox, otherwise let it pass through. You will still need some > script or tool to re-send any message that was mis-classified, but this is > probably some fairly trivial web app cgi. > >
Unfortunately, I need to do this a rung down. There's a couple of ways to send email (webmail for free, SMTP server access for paid, etc.) but all of them forward/relay mail out a bank of relatively generic servers running sendmail. So I was hoping to throw all of the SA integration there and catch all of the cases. But your suggestion of using procmail may still be valid here (but I'm not immediately sure how/if procmail will work inside of a mail relay as opposed to local delivery). I'll need to dig further. That's just "obvious" enough that I didn't even consider it. As for keeping the headers, I'm not completely opposed to that. But already a sadly surprising amount of the outbound spam that is getting sent is being scored at 4.9 (so I'll need to filter lower...). I suspect that would only get worse if more mailers knew they could just tune their messages to what I'm using. But, maybe with some Bayesian work... it would be possible. But, as I said, I'm a bit risk averse and Bayesian poisoning is so easy, especially at this volume. Thanks for your feedback. I wasn't aware of the report_safe option, but that's a good call too. Joe -- View this message in context: http://www.nabble.com/Outbound-spam-filtering-for-a-large-ISP-tf4368897.html#a12453881 Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
