On 6/26/2015 10:53 AM, Dave Wreski wrote:
On 06/26/2015 12:45 PM, Benny Pedersen wrote:
Alex Regan skrev den 2015-06-26 18:33:
http://pastebin.com/FzUkEvRp
blacklist_from *@*.allisonarctictrips.com
spf-pass take responselily
Yes, after it's received, there are a ton of things that could be done
to block it (including my local RBL). I was hoping for something
preventative.
Eh? I'm afraid I don't get this at all - greylisting and RBL checks in
the MTA before SA even sees it, are the only thing
out there that is even in the realm of preventative measures and you
already know about greylisting.
Are you not aware that once a DATA channel is opened on an SMTP
transaction that you have effectively "received" it?
You can load your RBL checks into the MTA itself and block it at the
IP level before issuing an ack on the handshake, or you can greylist
which also blocks it before issuing an ack on the handshake.
But, putting RBL checks into the MTA is the best way I know to piss off
your users since tag-and-forward is not an option on MTA rbl checking.
That's why we all do our RBL checks in spamassassin.
Ted
