For some domains,there are too many txt records under the main domain,for example.

oracle.com,it has more than 20 txt records,for the nameserver query,it only return several records but result not include the spf record,it may cause spf and dmarc check failure.

Same as walmart.com, dhl.com and etc,all have too many txt records.

You may say,to change the nameserver for the server,but it maybe works fine for this domain,but not for the other.

I hope there is function to set spf record for the domain under  config/LocalSPFCache.txt

dhl.com|v=spf1 include:dpdhl._spf.dhl.com include:3a._spf.dhl.com include:3b._spf.dhl.com include:3c._spf.dhl.com include:3d._spf.dhl.com include:3e._spf.dhl.com include:3f._spf.dhl.com include:mrsc._spf.dhl.com include:e2ma.net include:spf.mandrillapp.com ~all
walmart.com|v=spf1 include:_netblocks.walmart.com include:_vspf1.walmart.com include:_vspf2.walmart.com include:_vspf3.walmart.com ip4:161.170.248.0/24 ip4:161.170.244.0/24 ip4:161.170.241.16/30 ip4:161.170.245.0/24 ip4:161.170.249.0/24 ~all
oracle.com|v=spf1 include:spf_s.oracle.com include:spf_r.oracle.com include:spf_c.oraclecloud.com include:spf_x.oracle.com include:spf_z.oracle.com include:stspg-customer.com ~all

In that case,it can settle the SPF,DMARC failure issue.

There are too many IT do not know the txt will cause the email issue. They will add too many txt records under main domian but never delete after some website,app,sofeware validication.

I think this function is very useful to settle the spf and dmarc issue. Even you may say,the domain SPF may change,but it is not import,as you can also update it if found this is error.

Tommy,

It does not matter how many TXT records a domain has. They will most likely only have ONE record for SPF, which will start with string v=spf1. Every other record has a different purpose, and Xeams will ignore them when checking SPF. Therefore, as long as your DNS lookup returns every record, Xeams will only use the one that is needed (the one that starts with v=spf1).

I confirm your example (Walmart.com, dhl.com, and Oracle.com). They all have many records, but only one for SPF.

You are correct,these domain only have one SPF,the main problem is that,for some query,it only return 3-5 txt records,not all the records,in that case,the spf and dmarc has problem.

You can check dns with below nameserver,some only return few result without the SPF one.

dig oracle.com txt @180.184.1.1
dig oracle.com txt @223.5.5.5
dig oracle.com txt @119.29.29.29
dig oracle.com txt @114.114.114.114
dig oracle.com txt @8.8.8.8
dig oracle.com txt @208.67.222.222

What is the point of using a DNS server that does not return correct values? I see that the first few entries in your example are servers hosted in China. The last two servers are for Google and Cisco, respectively. They are returning correct results—at least when I ran the test.

The xeams is using for global,different country may use different DNS for the server.

In china,mainly are using 223.5.5.5,119.29.29.29,very few are using 8.8.8.8,208.67.222.222

In that case,it may have problem.

For korea,Japan,vietnam,most of case,also will not use 8.8.8.8,208.67.222.222