Short answer:
DMARC continues to work when using Xink server-side. Ensure SPF and DKIM are correctly configured, then add a DMARC record starting with policy p=none before moving to stricter enforcement.
What is DMARC?
DMARC (Domain-based Message Authentication, Reporting & Conformance) helps protect your domain from email spoofing by verifying that messages are sent from authorized sources.
It also helps prevent unauthorized use of your domain for spam or phishing.
When using Xink server-side (re-routing), your DMARC policy will continue to function as expected.
Before you start
Before configuring DMARC, make sure the following are set up and validated:
Both must be correctly configured for DMARC to work effectively.
Configure DMARC
Add a TXT record in your DNS for your domain:
TXT: _dmarc.yourdomain.com Value: "v=DMARC1; p=none"
Policy options:
- none – Monitor only (recommended starting point)
- quarantine – Send suspicious emails to spam
- reject – Block failing emails completely
Start with p=none to monitor results, especially if you use third-party email services. Once validated, you can move to quarantine or reject.
Test and validate
After adding the DMARC record:
- Send a test email and review the message headers
- Use an external validation tool:
Additional resources
Microsoft 365:
DKIM configuration
DMARC configuration
Google Workspace:
Turn on DMARC
