It depends if it is at connection time, or after the RFC5321.MailFrom where the SPF can be evaluated. If there is no valid rDNS and no SPF, rejecting after SPF evaluation may not be a bad solution, as anyhow in a great majority of cases it aint going to be fixed during all these retries, till the email bounces and someone notices... so why wait?
I contacted APNIC, they are checking the DNSSEC, but nevertheless, set SPF, it is simple to do... and nowadays a SPF fail is treated like a DKIM fail, i.e., like if there was no SPF set. https://www.linkedin.com/pulse/email-security-future-laura-atkins On Fri, Dec 4, 2015 at 4:25 AM, Tony Finch <d...@dotat.at> wrote: > Franck Martin <fmar...@linkedin.com> wrote: > > > > http://dnsviz.net/d/5.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.4.7.2.0.0.1.0.0.0.0.0.1.5.0.4.2.ip6.arpa/dnssec/ > > Gmail should treat that as a temporary error not a permanent one. > > Tony. > -- > f.anthony.n.finch <d...@dotat.at> http://dotat.at/ > Biscay: Southwesterly 5 or 6 in northwest, otherwise, northerly 4 or 5, > becoming variable 3 or 4. Moderate or rough, occasionally very rough later > in > northwest. Mainly fair. Good. > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop >
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
