Transactional mail via Mailgun/Postmark/SendGrid lands poorly, DKIM and SPF unclear
For solid delivery the sender (Mailgun/Postmark/SendGrid) must DKIM-sign for your domain, not theirs. That requires your own DKIM selector via CNAME or TXT in your zone, plus an SPF include or DKIM-only alignment in DMARC.
Try this first
- 1In the sender portal, create a sending domain for your own domain (mail.vectel.nl or vectel.nl), not their default.
- 2Place the supplied CNAME records (Mailgun uses smtp._domainkey, Postmark pm._domainkey, SendGrid s1._domainkey and s2._domainkey) in your DNS.
- 3Add the SPF include to your apex SPF (include:mailgun.org, include:spf.mtasv.net, include:sendgrid.net), watch the 10-lookup limit.
- 4Only enable sending in the portal once DNS resolves, otherwise their default domain signs and DMARC alignment breaks.
- 5Test with mail-tester.com from a test account, expect 10/10 with SPF, DKIM and DMARC all green.
When to bring us in
If you have many transactional senders and SPF gets long or DKIM messy, we can sort which vendor stays and which can run via a single relay.
See also
- Domain expires tomorrow and nobody saw the emailAn expired domain doesn't transfer instantly. There's a redemption window, but you pay extra.
- Unsure whether to enable auto-renewDisabling auto-renew only makes sense for domains you'll truly drop. For anything live, just keep it on.
- New registrar asks for auth code, can't find itEPP code or transfer code is the password to move a domain from registrar A to B.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.