Chapter 2 · 2.4
SPF and DKIM when you send via Gmail
Recipients check whether mail from your domain really comes from you. They do this with SPF (which servers may send mail on behalf of your domain), DKIM (a digital signature on every message) and DMARC (what the recipient does if those checks fail). If you send from your own address via Gmail, you'll want to know whether those checks pass.
Sending via our server? Then you don't need to do anything
With Send mail as and our SMTP server (see Sending from your own address in Gmail on your computer), your mail leaves through our server. Gmail logs in to our server and hands the mail over to us. That's why the normal records of your domain apply:
| Record | Default at WebOké |
|---|---|
| SPF | v=spf1 a mx include:webawere.nl ~all: all WebOké mail servers may send mail for your domain. |
| DKIM | Enabled by default: a TXT record with the name x._domainkey. Our server signs your mail. |
You do not need an SPF rule for Google for this. Only add include:_spf.google.com to your SPF record if you actually send via Google's servers, for example with Google Workspace. A domain may have only one SPF record. Add to the existing record rather than creating a second one (see Setting up and extending SPF).
Is your domain's DNS hosted elsewhere?
If your DNS is with another provider, such as Cloudflare, your SPF record there must contain include:webawere.nl. The DKIM record must also be there: copy the name x._domainkey and the full value from DNS Administration in DirectAdmin. See Enabling and checking DKIM.
Checking that it works
- In Gmail, send a message from your own address to another Gmail address of yours.
- Open the message and choose Show original from the three-dot menu.
- SPF, DKIM and DMARC should all show PASS.
You can also check your domain with the free Email Health Check. It shows whether MX, SPF and DMARC are set up correctly.
Forwarded mail and SPF
If you forward your mail to Gmail (see Forwarding mail to Gmail), mail from the original sender reaches Gmail from our server. To that sender's SPF record, our server is unknown. As a result, Gmail may treat the forwarded mail as spam. You can't fix this with your own SPF record. It's one of the reasons we recommend IMAP (see Forwarding or IMAP: which should you choose?).
Is your mail still landing in spam?
- Check that your DMARC record is in place. A plain-language explanation: What is DMARC? A plain-language explanation.
- Do you send a lot of mail, such as a newsletter? Gmail then has extra requirements. Read The requirements of Gmail, Yahoo and Microsoft for bulk senders. Use a newsletter service for newsletters.
- More causes: My mail ends up in the recipient's spam folder.