Hi Mauricio, On 2016-09-08 00:48, Mauricio Teixeira mauricio.teixeira@... [milter-greylist] wrote: > I have contacted them, but that's no the point. They're not the first > and won't be the last, and I am tired of managing an exception list. I > want things more automated. But at the same time I don't want to have > to remove the reverse DNS check, because that also blocks real issues. Beside the technical problem I'm asking myself what is the benefit of an extra acl for not matching rDNS, especially with a longer delay than that for standard greylisting? If the sending host is "valid" it has spooling and will break through greylisting even after your 120 minutes, as well a sending spambot with spooling. A fire and forget sender will be caught by standard greylisting. So why setting a longer delay for misconfigured forward confirmed DNS? Which brings me to the question, what is a good value for delaying at all? Ciao! Marcus
Message
Re: [milter-greylist] Greylisting Hosts Without Reverse DNS doesn't work
2016-09-07 by Marcus Schopen
Attachments
- No local attachments were found for this message.