On 22/10/16 17:27, /dev/rob0 wrote: > On Sat, Oct 22, 2016 at 11:19:36AM -0500, Paul Schmehl wrote: >> --On October 22, 2016 at 12:16:33 PM +0200 Paul van der Vlis >> <[email protected]> wrote: >>> Op 22-10-16 om 04:32 schreef Bill Cole: >>>> /127\.0\.0\.1/ REJECT you are not me >>> Thanks, a great idea to have standard in most cases. >> I would make one suggestion. I would reject the attempt silently. >> No sense in tipping off the spammer to what he needs to do to work >> around it. Just use REJECT with no explanation.
I have also had HELO statements announcing:- my own public-facing ip address (from the outside of my NAT firewall), spurious servers using my own domain name; example.com (!); and possibly more controversially, variations on localhost. *ALL* my own machines are accepted by permit_mynetworks, so anything else purporting to belong to me is a demonstrable lie. All the above are also rejected by my helo_access list. Allen C > The point of rejection messages is in case a human comes up against > it (and even this one, it could happen.) You need to let a novice > postmaster know what s/he has misconfigured. > > There is zero evidence over 2 decades that botnet spammers even have > the capability to receive and parse their rejection messages, much > less the interest in doing so.
