Gmail Delivery and SPF Records
Why email authentication matters
Gmail may reject unauthenticated email or mark it as spam. Google requires all senders to use at least SPF or DKIM. Bulk senders must meet additional requirements, including SPF, DKIM and DMARC.
EDIS added a standard SPF record to existing domains that had no SPF record and whose email service was managed by EDIS.
Understanding and configuring SPF
An SPF record specifies in DNS which servers may send email for a domain. Receiving mail servers use it to check whether the sending server is authorised for the domain being used.The TXT record added by EDIS for these existing domains is:v=spf1 a:spf.edis.at ~all~all means Softfail. A neutral result is indicated by ?all. -all means Fail. An SPF record alone does not guarantee delivery to Gmail.The record must account for every service you actually use to send email. If you use additional email providers or newsletter services, the configuration must reflect them.
The change applied only to domains that had no existing SPF record and whose email service was managed by EDIS. You can adjust the record to match your sending services in the DNS panel.Signing in to the PDNS panel
EDIS DNS administration with PDNS-AdminCheck DKIM and DMARC as well as SPF. Refer to Google’s current sender guidelines. RFC 7208 explains the technical details of SPF results.
EDIS DNS administration with PDNS-AdminCheck DKIM and DMARC as well as SPF. Refer to Google’s current sender guidelines. RFC 7208 explains the technical details of SPF results.