How to set up DMARC/DKIM/SPF for MXOF Mail Relay

Set up MXOF Mail Relay by authorizing your sending domain with MXOF, publishing the SPF authorization and DKIM records supplied for your account, and adding a DMARC TXT record. Configure a custom Return-Path under your domain for SPF alignment. DMARC passes when SPF or DKIM passes with domain alignment to the visible From address.
I start with the domain used by the application, then test a delivered message through the same relay route. MXOF must supply the actual verification values and DKIM selector; the examples below are not account credentials or universal MXOF settings.
Add your domain
Have access to your authoritative DNS zone and the administrator responsible for your MXOF relay account. I get the domain approved for outbound sending before changing the application.
- Request authorization. Ask your MXOF administrator to enable your exact From domain, such as example.com, for your relay account. Request the ownership verification record if verification is required.
- Publish the challenge. At your DNS host, create the TXT or CNAME record supplied by MXOF. Copy the name and value exactly, then ask MXOF to confirm that domain authorization is complete.
- Request authentication values. Obtain the SPF include or approved outbound IPs, DKIM selector and public DNS value, plus the custom Return-Path instructions. Ask which settings require MXOF support to activate them.
- Connect the application. Use the SMTP endpoint, port and authentication method assigned to your account. Require TLS and set the visible From address to the approved domain. Do not use an rDNS hostname as a guessed SMTP endpoint.
Keep receiving mail separate
Adding outbound authentication does not require replacing your domain's existing MX records. A dedicated Return-Path subdomain sometimes needs provider-specified MX records for bounce handling; apply those only at the exact name MXOF supplies.
Set up SPF
MXOF supports Return-Path alignment. I configure it explicitly because an SPF pass for a provider-owned Return-Path does not establish SPF alignment with your From domain.
- Choose the envelope domain. Ask MXOF to use an address under your domain for SMTP MAIL FROM, for example bounce@bounces.example.com. The receiving server normally records this address in Return-Path.
- Publish the assigned records. Use the exact TXT, CNAME or bounce-routing records supplied by MXOF. SPF is evaluated at the MAIL FROM domain, so a record at example.com does not cover bounces.example.com automatically.
- Merge authorization. If MXOF requires a TXT record, keep one v=spf1 record at that name. Add its confirmed mechanism before the existing all mechanism and retain other legitimate senders. Keep SPF evaluation within the 10 DNS-lookup limit, including nested includes.
- Activate the Return-Path. Have MXOF confirm the custom envelope domain is active. Send application mail and check that smtp.mailfrom uses your domain and SPF passes.
Conditional example: TXT value only if MXOF confirms this includetext
v=spf1 include:spf.prxy.com -all
Use that example only if MXOF explicitly assigns include:spf.prxy.com to your relay account and MXOF is the only authorized sender at the chosen DNS name. Otherwise use the supplied authorization and preserve your existing senders.
Enter the actual MAIL FROM domain into the SPF checker below. If MXOF supplies a CNAME delegation, publish that CNAME exactly; a CNAME cannot coexist with an SPF TXT record at the same name.
SPF checker
Find SPF syntax issues, lookup limits, and weak records.
?/16tests passed
With the default relaxed DMARC SPF alignment, bounces.example.com matches a visible From domain of example.com because both share the same organizational domain. With aspf=s, the domains must match exactly.
If a received message still uses an MXOF-owned envelope domain, ask MXOF to correct the Return-Path configuration. DMARC can still pass through DKIM with domain alignment while that SPF alignment issue is being resolved.
Set up DKIM
DKIM requires both a published public key and active signing on the sending system. I check the delivered signature instead of treating a DNS lookup as proof that signing is enabled.
- Request domain signing. Ask MXOF to sign messages using your From domain, or a subdomain that meets your DMARC DKIM alignment setting. Request a 2048-bit RSA key where supported.
- Copy the selector record. Publish the exact TXT public key or CNAME target MXOF supplies at its specified selector._domainkey name. Do not invent a selector or publish a private key.
- Enable signing. After DNS resolves, ask MXOF to activate DKIM for the domain and the application relay route. If MXOF requires application-side signing, confirm that requirement before proceeding.
- Inspect a fresh message. Check DKIM-Signature for d= and s=. Confirm dkim=pass in the receiving server's Authentication-Results and verify that d= matches your From domain under the applicable DMARC rules.
DNS lookup examples: replace mxofselector with the assigned selectorbash
dig +short TXT mxofselector._domainkey.example.com dig +short CNAME mxofselector._domainkey.example.com
Under relaxed DKIM alignment, a signing domain under example.com matches a From domain of example.com. With adkim=s, use the exact From domain. A valid signature belonging only to mxof.com does not satisfy DKIM alignment for example.com.
An SPF alignment failure is compatible with a DMARC pass when DKIM passes with domain alignment. An authentication pass alone is not enough; the authenticated domain matters.
DKIM meets DMARC
From domain: example.com. DKIM d=example.com and dkim=pass. This satisfies DMARC through DKIM even if SPF has no domain alignment.
DKIM needs correction
From domain: example.com. DKIM d=mxof.com and dkim=pass. That signature alone does not satisfy DMARC for example.com.
Set up DMARC
Publish DMARC for your visible From domain, rather than your relay hostname. I start with reporting for a domain that has no enforcement policy. If you already use p=quarantine or p=reject, keep that policy while configuring MXOF.
- Inspect the existing policy. Look up TXT records at _dmarc.example.com. Edit the existing DMARC record rather than creating a second one at the same name.
- Prepare a reporting destination. Create a working mailbox or use the reporting address assigned by your report processor. Replace the example address below with that destination.
- Publish monitoring mode. For a domain without enforcement, add the example TXT value at _dmarc.example.com, substituting your actual domain and reporting mailbox. Keep existing enforcement if already enabled.
- Check reporting authorization. If rua points to another domain, have the report recipient confirm the required external reporting authorization in its DNS. Then validate the published policy.
Monitoring example: TXT at _dmarc.example.comtext
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Use the DMARC record generator to build the record with your actual reporting destination. Publish one complete DMARC TXT value; do not add the example as an additional policy.
Enter the visible From domain into the DMARC checker below after saving DNS. This checks the policy; a delivered test message is still needed to verify MXOF authentication.
DMARC checker
Look up a domain's DMARC record and catch policy issues.
?/7tests passed
The p=none policy requests monitoring without DMARC enforcement. It does not guarantee inbox placement or stop a receiver applying its own filtering rules.
Allow DNS caches to expire according to the previous TTL. Aggregate reporting is typically daily, so a successful test email appears sooner than the corresponding report.
Verify and troubleshoot
I test a real application notification through MXOF after each change. A message sent through a different SMTP route does not validate the application's configuration.
- Send through the application. Trigger a transactional message using the approved From domain. Keep the full received headers and the relay's delivery log for the same message.
- Read receiver results. Use Authentication-Results added by the final receiving system. Check spf, smtp.mailfrom, dkim, header.d and dmarc against the actual From domain.
- Check the DNS owner. Query the full record name and confirm the DNS host has not appended your domain twice. For DKIM CNAME records, confirm the target resolves to the expected key.
- Retest after the fix. Send a new message after the DNS TTL expires. Test each application route and each sending domain before changing the DMARC enforcement policy.
|
|
|
|---|---|---|
SPF permerror | Duplicates or lookups | Merge; recount lookups |
SPF no match | MAIL FROM domain | Activate custom domain |
DKIM absent | Relay signing | Enable domain signing |
DKIM fail | Key or modification | Check selector and logs |
DMARC fail | Domain alignment | Compare From and results |
No reports | rua delivery | Check mailbox and DNS |
Use the receiver's result to choose the next check.
For a fast check, use the email tester below. It gives you a destination address; send to it through the application and MXOF, then inspect the authentication diagnosis.
Compare the detected Return-Path and DKIM signing domain with the visible From domain. The useful outcome is a DMARC pass through SPF or DKIM with domain alignment.
Email tester
Send a real email to this address. Suped shows a results button when the test is ready.
?/43tests passed
A successful test validates that message and route. Repeat it for any separate application credentials, From domains or relay pools that your production traffic uses.
If authentication passes but delivery still fails, inspect the SMTP response and reputation signals. A blocklist (blacklist) listing is a separate problem; changing DMARC alone does not remove a listing.
Get alerted when it breaks
Suped is our DMARC reporting and email authentication platform. For MXOF traffic, its practical role is detecting authentication failures after setup and keeping the source-specific evidence available for investigation.
- Keep reports flowing. Retain the report recipient assigned to your monitoring service in rua. Without reports, there is no aggregate MXOF traffic to diagnose.
- Enable issue emails. In Suped's Notifications settings, enable Issues detected and Sending sources need verification. Send these notifications to the person responsible for the relay and DNS.
- Review MXOF failures. Use Suped's source table to inspect MXOF traffic. Open failing records in Detail view and compare SPF, DKIM and DMARC results with the affected application's headers.
- Verify the repair. Follow the detected issue's fix steps, retest the application and check subsequent reports. Use DNS history to investigate unexpected changes to authentication records.
Our DMARC monitoring workflow combines source review with detected issues and notifications, so the team can investigate an MXOF failure without manually reading each aggregate XML report.
DMARC notifications depend on receiver reports reaching Suped. Keep application delivery-error alerts enabled as well, because SMTP failures often need attention before aggregate reports arrive.
Secure your domain with p=reject
I move to enforcement only after every legitimate sender using the domain has a working DMARC path. MXOF passing one test is insufficient if another application still sends unauthenticated mail.
- Verify all legitimate sources. In Suped, review verified and unverified sources. Match MXOF traffic to your application logs and resolve failures for every other authorized sender.
- Cover a full sending cycle. Include password resets and low-volume jobs, plus scheduled messages such as monthly statements. Require passing SPF or DKIM with domain alignment for every legitimate route.
- Stage enforcement. Change p=none to p=quarantine, review receiver reports and delivery errors, then move to p=reject after legitimate failures are resolved. Keep rua in place throughout.
- Keep watching. Use Suped issue notifications after enforcement and retest when MXOF changes selectors or relay infrastructure. Review subdomain policy deliberately before applying a parent policy broadly.
Enforcement example: update the existing TXT policytext
v=DMARC1; p=reject; rua=mailto:dmarc@example.com
Suped's Hosted DMARC lets your team manage the published policy through our dashboard after its DNS delegation is configured. Pair policy changes with Suped's source diagnostics to check the effect on legitimate MXOF traffic.
Keep the actual report destination in your enforcement record. A p=reject policy requests rejection of messages that fail DMARC; receivers retain their own handling decisions, and DMARC does not prevent lookalike-domain impersonation.
Frequency asked questions
Use the include or outbound IP authorization assigned by your MXOF administrator. Use include:spf.prxy.com only if MXOF confirms it for your account. Do not guess include:mxof.com or copy another customer's record. Publish SPF for the actual MAIL FROM domain and preserve other authorized senders.
The mxof.com suffix is a clue to MXOF Mail Relay infrastructure. Treat that attribution as provisional until the connecting IP, forward and reverse DNS, received headers and your account logs agree. An rDNS suffix does not prove that the sender is authorized or that the message passes DMARC.
SPF checks the SMTP MAIL FROM domain. If that domain belongs to MXOF rather than your organization, SPF can pass without domain alignment to your visible From address. Activate MXOF's custom Return-Path configuration. DMARC still passes if DKIM passes with domain alignment.
Yes. A passing DKIM signature with domain alignment is sufficient for DMARC, even when SPF fails. Forwarding often breaks SPF, so verify DKIM on received messages. If both SPF and DKIM fail to provide authentication with domain alignment, DMARC fails.
No. MXOF must sign messages using the matching private key, or explicitly require signing on your sending system. Confirm that a delivered message has a DKIM-Signature with the expected d= and s= values and that the receiving system reports dkim=pass.
Keep p=reject while configuring MXOF. Approve the domain, publish the assigned authentication records and test the application route before production use. The p=none example is for domains starting without enforcement, not a prerequisite for adding a relay.

