dns,aktau

dns's People

Contributors

Watchers

dns's Issues

SPF mail setup

After c471c24 (publishing a TXT record alongside an SPF record), I see the following from dkimvalidator.com:

SPF Information:

Using this information that I obtained from the headers


Helo Address = mail-wm0-f54.google.com
From Address = [email protected]
From IP      = 74.125.82.54
SPF Record Lookup


Looking up TXT SPF record for hillegeer.com
Found the following namesevers for hillegeer.com: ns5.luadns.net ns4.luadns.net ns3.luadns.net ns2.luadns.net ns1.luadns.net
Retrieved this SPF Record: zone updated 20160802 (TTL = 3136)
using authoritative server (ns5.luadns.net) directly for SPF Check
Result: pass (Mechanism 'include:_spf.google.com' matched)


Result code: pass
Local Explanation: hillegeer.com: Sender is authorized to use '[email protected]' in 'mfrom' identity (mechanism 'include:_spf.google.com' matched)
spf_header = Received-SPF: pass (hillegeer.com: Sender is authorized to use '[email protected]' in 'mfrom' identity (mechanism 'include:_spf.google.com' matched)) receiver=ip-172-31-3-128.us-west-1.compute.internal; identity=mailfrom; envelope-from="[email protected]"; helo=mail-wm0-f54.google.com; client-ip=74.125.82.54

So now it passed. Apparently that was it. Perhaps luadns does something funky with SPF records? It doesn't really seem so, the dig(1) output for the TXT record is exactly the same as for the SPF record:

$ dig hillegeer.com any | grep -P 'TXT|SPF'
hillegeer.com.      3594    IN  TXT "v=spf1 a mx include:_spf.google.com ~all"
hillegeer.com.      3594    IN  SPF "v=spf1 a mx include:_spf.google.com ~all"

Recommend Projects