Three DNS records decide whether mail from your domain reaches the inbox: SPF names the servers allowed to send, DKIM signs each message and DMARC tells receivers what to do when both fail to line up with your From address. Publish them in that order, check each one, and tighten DMARC only after the reports are clean.
What each record does
| Record | Where | Job |
|---|---|---|
| SPF | TXT on the domain | Lists the servers allowed to send for it |
| DKIM | TXT on a selector, such as dkim._domainkey | Public key that verifies each message signature |
| DMARC | TXT on _dmarc | Policy for failures and an address for reports |
For EuroVDC Corporate Email the baseline is MX securemail.eurovdc.eu at priority 10, SPF v=spf1 mx ip4:45.84.90.12 -all and the DKIM value from your DNS wizard. The records belong in the zone of the From domain, wherever the website is hosted.
Rollout in four steps
- SPF. One record only. Two SPF strings break the standard. Stay under 10 DNS lookups when you add other senders.
- DKIM. Copy the full value from the wizard. If your DNS panel appends the domain automatically, do not type it twice in the host field.
- DMARC at monitoring. Start with
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.comand read the reports for a couple of weeks. - Tighten. Move to
p=quarantine, thenp=rejectonce every legitimate sender passes.
Alignment is the part people miss
DMARC passes when SPF or DKIM passes and the authenticated domain matches the visible From domain. A form plugin or billing tool that sends as you@yourdomain.com from the vendor’s envelope domain passes SPF for the vendor and fails DMARC for you. Fix it by authorising the tool in SPF or by aligning its DKIM to your domain.
Third-party senders
Newsletters, CRMs and ticket systems each need an entry or their own aligned DKIM. List every system that sends as your domain before you move DMARC beyond p=none. A tool you forgot is the usual reason a strict policy starts rejecting real mail. The rejection message when it goes wrong is explained in Gmail 5.7.26 with SPF present.
Client ports and server names are in SMTP and IMAP setup, the record reference in SPF, DKIM, DMARC and deliverability, and the product is corporate email.
Frequently asked questions
SPF -all or ~all?
Use -all for a mailbox domain where you control every sender. Use ~all while you are still discovering senders.
Can SPF alone pass DMARC?
Yes, if it aligns. Forwarding often breaks SPF, so publish DKIM too.
How long should p=none run?
Long enough to see every regular sender in the reports, typically two to four weeks.
Where do the DMARC reports go?
To the address in rua. Use a mailbox that someone reads, or a report-processing service.




