Greylisting would just mean the first one would be delayed - the rest would
go through as they are identical emails.
I would be looking to use Fail2ban as a solution depending on what your
logs show.
*** REPLY SEPARATOR ***
On 2/09/2011 at 12:14 PM John Hardin wrote:
>On Fri,
On Fri, 2 Sep 2011, Steve wrote:
I wonder, would it be possible to reject an email identical (same
originating IP; same addressee; same subject) to an email received in
the last minute, say, that had a spamassassin score of over 30? If I
could find a way to do that, I could reduce the volume of
On Fri, 02 Sep 2011 15:13:32 +0100, Steve wrote:
Does anyone do this already?
spamassassin is not currently designed for this kind of sender
tracking, but it could be in next version if one make the needs plugins
:=)
currently only option you have is to use policyd v2 to make what you
lik
On 9/2/11 10:13 AM, Steve wrote:
could find a way to do that, I could reduce the volume of spam I have to
process/store by a factor of about 8. Rejecting only emails with
credentials identical to known recent highly scoring spam would make the
risk of false positives minimal.
Does anyone do thi
There is something curious I've noticed... I'm wondering if I'm unique,
and if there's an obvious way to improve my setup.
I was thumbing through my spam folder, and noticed that the bulk of my
spam conformed to a very obvious pattern... On a time period from
minutes to hours, I receive nine ident
