> On 21 Dec 2020, at 21.16, Kevin A. McGrail via mailop <[email protected]> > wrote: > > On 12/21/2020 1:56 PM, Eric Tykwinski via mailop wrote: >> Just a heads up: >> >> v=spf1 include:spf2.bluehost.com include:_spf.qualtrics.com >> include:_spf.google.com include:_spf.salesforce.com >> include:sparkpostmail.com include:spf.mailjet.com -all >> >> evaluating... >> Results - PermError SPF Permanent Error: Too many DNS lookups >> > Side-note: In general, the RFC for SPF is too strict on this. SA raised the > limit from 10 to 20 because otherwise you get all kinds of real-world > failures. >
It would be a REALLY good idea to raise this limit - people are no longer sending mail from simple setups, they are using all kinds of external services causing SPF to fail due to hitting the limit :-/ And with a card-tower of other standards being dependent on a SPF pass, that fail due to the limit of 10 DNS lookups is counter-productive. The RFC says: SPF implementations MUST limit the total number of those terms to 10 during SPF evaluation, to avoid unreasonable load on the DNS. If this limit is exceeded, the implementation MUST return "permerror". Is this still a valid limit? I’d like to hear your thoughts about it. Kind Regards, Sidsel Jensen Team manager Mail & Abuse, Systems Engineer @ One.com <http://one.com/>
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ mailop mailing list [email protected] https://list.mailop.org/listinfo/mailop
