On Wed, 8 Feb 2006, John Peacock wrote:
Charlie Brady wrote:
I don't want to waste my time talking to a spambot claiming to be
"aol.com". And there a big chance that he will ignore my 550 code, and
will send me the message anyway.
Except that qpsmtpd won't continue to play with that server (i.e. every
subsequent line will be refused).
I realise that. But that will still chew up my bandwidth, CPU and VM.
I'm actually looking at this with require_resolvable_fromhost, which
actually does (currently) a DENY_SOFT, which is even more wrong.
I'm not sure of that. Having an unresolvable fromhost can still happen for
legitimate mail, in case of DNS misconfiguration. But there shouldn't be
anything wrong with DENYSOFT_DISCONNECT.
I think what we need is a "three-strikes" meta plugin: ...
Perhaps - but should spam_checkhelo use DENY_DISCONNECT?
