Problem description: When we test our email using Mailtester, we encounter unusual numbers for our project, namely.
SPF record:
v=spf1 include:dc-aa8e722993._spfm.autov.be include:_spf.firebasemail.com include:_spf.google.com ~all
more information:
autov.be: Included domain 'dc-aa8e722993._spfm.autov.be' has no applicable sender policy
Details:
dig +short TXT autov.be :
- "firebase=autov-db5f7"
- "google-site-verification=1PiQrkRmbdiLoOsX_DeQSBmf6xQ1qFedQA2QpaIfRZo"
- "v=spf1 include:dc-aa8e722993._spfm.autov.be include:_spf.firebasemail.com include:_spf.google.com ~all"
- "firebase=autov-db5f7"
- "google-site-verification=1PiQrkRmbdiLoOsX_DeQSBmf6xQ1qFedQA2QpaIfRZo"
- "v=spf1 include:dc-aa8e722993._spfm.autov.be include:_spf.firebasemail.com include:_spf.google.com ~all"
- permerror
- autov.be: Included domain 'dc-aa8e722993._spfm.autov.be' has no applicable sender policy
- autov.be: Included domain 'dc-aa8e722993._spfm.autov.be' has no applicable sender policy
- Received-SPF: permerror (autov.be: Included domain 'dc-aa8e722993._spfm.autov.be' has no applicable sender policy
According to the documentation, there should only be one record, and this combination already looks strange. So, I removed the SPF record that was at the bottom. The issue is that you can only test it properly tomorrow because it needs 24 hours. Now, the SPF record looks as follows.
After update
Links about SPF and Google services
https://apps.google.com/supportwidget/articlehome?article_url=https%3A%2F%2Fsupport.google.com%2Fa%2Fanswer%2F10685031&assistant_id=generic-unu&product_context=10685031&product_name=UnuFlow&trigger_context=a
https://apps.google.com/supportwidget/articlehome?article_url=https%3A%2F%2Fsupport.google.com%2Fa%2Fanswer%2F10683907&assistant_id=generic-unu&product_context=10683907&product_name=UnuFlow&trigger_context=a
Comments
Post a Comment