|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: efficient blocking method question
From: /dev/rob0 (rob0
gmx.co.uk)
Date: Fri Aug 04 2006 - 18:45:04 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Friday 04 August 2006 18:19, Joey wrote:
> OK we are blocking email coming from blueyonder.co.uk via the
> client_access file.
You might want to move that up before the greylisting policy.
> Is this the best place to block this or should we have done it in
> header checks?
Absolutely! (That is, if blocking Blueyonder is a good thing, and I
won't comment on that except to say I wouldn't do it.)
> Also if you can elaborate why so that I can better understand.
You need to understand a bit about how SMTP works. Your
check_client_access lookup takes place before DATA (specifically, at
RCPT TO:.) Thus the message body is not transmitted. And perhaps more
importantly ...
> --- if in header checks would have done this (header_checks)----
> /^(To|From|Cc|Reply-To):.blueyonder\.co\.uk/ REJECT Header Spam
... this makes an assumption, which is not necessarily valid, that
"blueyonder.co.uk" is going to appear in (and ONLY in) the headers of
mail originating from there.
Again, you need to understand how SMTP works. If you don't, the
explanations won't make much sense.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]