On 2018-04-18 17:49, Al Iverson wrote:
In the past I've had to deal with DNSBL listings based on faked received headers-- IMHO, it's not safe to parse IPs beyond connections that you yourself have verified.
I've always considered this a feature, not a bug. Spammer forges their way into getting caught by a DNSBL? Good.
Legitimate mail forges received headers and hits a DNSBL? They just lost their legitimate status by forging Received headers, so my sympathy is probably busy that day.
Am I missing a case where there is a negative outcome to a legitimate, by-the-book sender?
(Obviously this needs to be applied to very selective DNSBLs, carefully excluding lists of end-user gear and other "Does not send mail" lists since these senders did the correct thing and used a smarthost).
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
