EASY steve.h...@digitalcertainty.co.uk wrote, at 06/23/2009 09:12 AM:
> Joey wrote:
>>> Actually, I use a header_checks rule:
>>>
>>> /X-Spam-Level: \*{5,}/ REJECT
>
> I wrote;
>> I looked at this myself and asked 'hang on, what if I put a header
>> filter in for X-Spam-Level'. I assumed (and that is all it was) that it
>> was not fed into the content filter until *after* Postfix had accepted
>> the whole message. ? ? If that is the case and it tried to bounce this
>> I'm not entirely sure of the carnage this would create. I'll have to
>> play with it as this looks like to easy and obvious to miss!
>
> And yep, having tested it - that does not work as intended;
> 250 2.0.0 Ok: queued as C4E83AC0C6
>
> So it takes it and then has to bounce it :-(
>
> It then tries to 'bounce' and could end up joe-jobbing some innocent
> person. I just did.....
I assume you tested it with your current after-queue content filter. You
must use it with a before-queue content filter (AKA smtpd proxy):
http://www.postfix.org/SMTPD_PROXY_README.html
Set up spampd as a before-queue content filter, and header/body_checks
will reject during SMTP.
