Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

PermError SPF Permanent Error: Too many DNS lookup

I have SPF and TXT record configured. When i check the SPF record syntax. It says PermError SPF Permanent Error: Too many DNS lookup.

 v=spf1 include:_spf.google.com include:netcore.co.in ~all 

And my emails are landed in SPAM as well.

1) I am on shared hosting, I dont have dedicated IP and DKIM configured. Actually I dont send emails with spam triggering words. Since I am on shared hosting. Is there any possibility of other's on the shared hosting sending the emails which resulted in my emails to land in SPAM.

2) I am using the netcore.co.in to send the mass mails. and google.com to send the mails from gmail. And I have properly configured MX records as well. I have mentioned google MX records But not netcore.net MX records. I am using sendgrid's free smtp server to send the emails from my java web app. which i am not mentioned in spf record. Is SPF record causing the spam issues.

like image 413
n92 Avatar asked Mar 27 '13 05:03

n92


People also ask

How do I fix too many DNS lookup SPF?

If there are too many SPF lookups you can use the SPF delegation tool in order to resolve the “Too many lookups” issue, replace your existing policy with the one provided by the DNS delegation tool. The DNS delegation tool will keep the SPF record up to date whenever one of the included ESPs change their records.

How many lookups can an SPF record have?

Many people may not realize it, but the Sender Policy Framework (SPF) specification has a limit on the number of DNS lookups (10) required to fully resolve an SPF record. One typically quickly exceeds this limit through the reckless use of the include modifier.

What does SPF PermError mean?

PermError means the published SPF record could not be verified by the mailbox provider. PermErrors are usually caused by a syntax or format error in the SPF record. Ensure your SPF record is set up correctly and doesn't have any extra spaces or unrecognizable characters in the DNS TXT record.


2 Answers

You should have a look at this question I answered a few weeks ago:

Too many DNS lookups in an SPF record

You only get 10 DNS lookups for SPF (that's part of the protocol). There are automatically two lookups to get your TXT records and the actual SPF record. Without doing the actual math (I'll leave that to you as an exercise), you're hovering in the neighborhood of 13-14 lookups. You need to either consolidate your SPF records into one, or drop one of those services. (For instance, SendGrid allows you to do both transactional and mass mail under one set of IPs, so you could drop netcore or gmail entirely).

As for your spam issue, you should contact SendGrid support (http://support.sendgrid.com), that shouldn't be happening to you and they will be able to help you troubleshoot and resolve the issue.

like image 188
Swift Avatar answered Oct 06 '22 10:10

Swift


Another option is to use an SPF Proxy service like spfproxy.org. It masks all the lookups behind a proxy that does it in the background. Takes just a couple minutes to setup. =

like image 20
AngularNerd Avatar answered Oct 06 '22 09:10

AngularNerd