On Sat, 03 Sep 2011 13:57:39 +0930, Peter Nitschke wrote:
Greylisting would just mean the first one would be delayed - the rest
would
go through as they are identical emails.
policyd v2 is designed for this
I would be looking to use Fail2ban as a solution depending on what
your
logs show.
last resort
if fail2ban filter<rulename>.conf checks spamassassin awl is below 5
then not make ip delayed in fail2ban save data to postfix client access
table, this could be very cool :)
this way one only hits spam senders, not ham sender, just need /32 ipv4
tracking in awl db
