How to set up DMARC/DKIM/SPF for TailoredMail

Updated on 25 Oct 2026: We revised the TailoredMail setup steps for current DMARC policy rollout, subdomain inheritance, and report-based alerts.
TailoredMail supports SPF and DKIM authentication, with DMARC checking the authenticated domains against the visible From domain. Use a dedicated sending subdomain, request the account-specific DNS record set from TailoredMail, publish every value exactly, and verify a live campaign before increasing enforcement.
TailoredMail's published delivery information describes custom domains and authentication support. Request your account's SPF hostname or include, DKIM selector, and record targets from the assigned account manager; do not copy another customer's records.
Add your domain
Use the same organizational domain for the visible From address and at least one DMARC authentication path. A practical pattern is news@example.com for the From address, bounce.example.com for the return-path, and a DKIM signing domain under example.com.
- Choose the identity. Pick the exact From domain, return-path subdomain, and DNS zone that will carry the records. Using a dedicated From subdomain gives marketing its own DMARC policy scope.
- Open account setup. Add the custom From address through the sender controls available in your account, or ask your assigned account manager to configure it.
- Request alignment. Ask which custom return-path and DKIM signing options are available for your account, then request identities with DMARC alignment to the From domain. Sender-address verification alone does not establish DMARC alignment.
- Collect the record set. Copy the record type, host, value, selector, and expected status for every entry. Keep the supplied values in a change ticket before editing DNS.
- Confirm ownership. Complete any sender-address confirmation, publish the requested ownership record, and keep the domain pending until TailoredMail reports it as verified.
Follow the account manager's instructions for your account. Confirm the custom From identity and the exact DNS package for each supported authentication path before editing DNS.

TailoredMail custom sender and domain setup screen
Do not switch production campaigns to the new From domain yet. Finish SPF, DKIM, and DMARC publication first, then send a controlled test through the same TailoredMail account and delivery stream used in production.
Set up SPF
SPF (Sender Policy Framework) authenticates the envelope sender, not the visible From address. Ask TailoredMail whether your account supports a custom return-path under your domain, and obtain SPF authorization for that exact hostname.
- Get the exact value. Ask TailoredMail for the custom return-path hostname and the required CNAME or SPF include target. Do not authorize IP addresses found in one test message.
- Check the host. If TailoredMail delegates bounce.example.com by CNAME, publish that CNAME at the bounce host. If it supplies an include term for an existing SPF record, merge the term into that one record.
- Keep one SPF record. Never publish a second record beginning with v=spf1 at the same hostname. Multiple SPF records cause a permanent error.
- Stay within the limit. Count DNS-querying terms across nested includes and redirect chains. The SPF lookup limit is 10 such terms per evaluation; exceeding it returns permerror.
- Preserve other senders. Retain every approved sender already present in the SPF record. Insert any TailoredMail include before the final all mechanism, and keep the existing all qualifier during the initial test.
Illustrative TailoredMail SPF structuredns
v=spf1 include:TAILOREDMAIL_VALUE ~all
Do not mix CNAME and TXT data
If TailoredMail gives you a CNAME for bounce.example.com, that hostname cannot also have an SPF TXT record or other DNS data. Publish the supplied delegation exactly and let its target provide the SPF answer.
The sample above shows structure only. Replace TAILOREDMAIL_VALUE with the account-specific target TailoredMail supplies, and use the separate return-path subdomain if the platform provisions one.
SPF checker
Find SPF syntax issues, lookup limits, and weak records.
?/16tests passed
Run the checker against the exact return-path domain, not only the root domain. A syntactically valid root SPF record does not prove that a TailoredMail message will pass aligned SPF.
Set up DKIM
DKIM (DomainKeys Identified Mail) is the more stable DMARC path because forwarding often breaks SPF while an unchanged signed message can retain a valid DKIM signature. TailoredMail advertises DKIM support; confirm that signing is active with a domain that has DMARC alignment with the From domain.
- Enable custom DKIM. Ask TailoredMail to sign with example.com or a subdomain beneath it. A signature using only a TailoredMail-owned domain can pass DKIM but will not match From: news@example.com under DMARC alignment.
- Copy every selector. Record each selector and whether TailoredMail expects CNAME or TXT. Publish all selectors when it supplies more than one, because multiple selectors allow safe key rotation.
- Enter the host once. Many DNS panels append the zone automatically. Check the resolved name so it does not end with example.com.example.com.
- Verify the target. Use TailoredMail's verification action if it appears in your account. Otherwise, ask the assigned account manager to confirm that signing is active after DNS resolves.
- Retest after rotation. Keep the old selector available until messages signed with the new selector pass and the lifetime of older messages has elapsed.
Illustrative DKIM CNAME recordsdns
selector1._domainkey.example.com CNAME TAILOREDMAIL_DKIM_TARGET_1 selector2._domainkey.example.com CNAME TAILOREDMAIL_DKIM_TARGET_2
These are placement examples, not TailoredMail production targets. Replace the selector names and targets with the values supplied for your account. Do not invent selectors or copy the targets from a different TailoredMail customer. For a TXT record, publish only the supplied public key value; the private key stays with the sender. The DKIM specification describes the public key lookup used for verification.

TailoredMail DKIM record and verification view
One aligned pass satisfies DMARC
A TailoredMail message passes DMARC when aligned DKIM passes or aligned SPF passes. Aim for both, but a valid aligned DKIM signature can keep DMARC passing when forwarding breaks SPF, provided the signed content survives unchanged.
Set up DMARC
For From: news@example.com, publish DMARC at _dmarc.example.com. It evaluates alignment with the visible From domain. Start a new deployment at p=none only after checking for existing or inherited enforcement. If p=quarantine or p=reject already applies, keep that policy and fix TailoredMail without downgrading protection.
- Find the current record. Query _dmarc.example.com before editing DNS. Modify the existing DMARC TXT record instead of publishing a second one.
- Start with observation. For a domain without existing or inherited enforcement, use the p=none example below with a real reporting destination ready to receive aggregate XML reports.
- Keep enforcement in place. If p=quarantine or p=reject is already published, leave it in place. Validate TailoredMail on a controlled campaign and correct its aligned identity.
- Configure report delivery. Send aggregate reports to a monitored destination and retain existing required rua addresses. If a destination uses another domain, confirm that external reporting authorization is published there.
- Leave alignment relaxed. Default relaxed alignment accepts an authenticated TailoredMail subdomain under the From domain. Use strict alignment only when every production stream has been tested for an exact domain match.
Initial DMARC TXT valuedns
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Use our DMARC record generator to build the value and add optional tags without breaking syntax. Publish the result as a TXT record at the _dmarc host in the From domain's DNS zone.
DMARC checker
Look up a domain's DMARC record and catch policy issues.
?/7tests passed
Check the From domain after DNS propagation. If verification stays pending, compare authoritative DNS with cached answers and allow the previous TTL to expire. Confirm that one valid DMARC record resolves with the intended policy and report destination. Syntax validation does not prove TailoredMail alignment, so the live-message test remains required.
DMARC is evaluated per message
Publishing p=none does not configure TailoredMail. It tells receivers to report results without requesting quarantine or rejection. TailoredMail still needs aligned DKIM or aligned SPF on every relevant campaign stream.
Check DMARC policy for subdomains
For newsletter@news.example.com, check _dmarc.news.example.com. A valid record there takes precedence over inherited policy. Without one, a standard example.com deployment applies its sp policy to existing subdomains, or p when sp is absent.
- A custom return-path such as bounce.example.com does not create a separate DMARC policy for From: news@example.com.
- Keep existing enforcement when onboarding a sending subdomain. Check inherited policy before adding a local record that reduces protection.
Verify and troubleshoot
DNS lookup results are necessary but not sufficient. Send a new TailoredMail campaign to a mailbox you control, then inspect that exact message's Authentication-Results, Return-Path, DKIM-Signature, and From fields.
- Use the production path. Send through the same TailoredMail account, custom From address, campaign type, and IP pool that production will use. A test sent by another mail system proves nothing about TailoredMail.
- Read the receiver result. Read Authentication-Results added by the receiving mailbox's trusted server. Find dmarc=pass first, then identify whether the pass came from aligned SPF, aligned DKIM, or both.
- Compare domains. Under relaxed alignment, the SPF smtp.mailfrom domain or DKIM d= domain must share the From domain's organizational domain. With aspf=s or adkim=s, the corresponding domain must match exactly. A raw pass with an unrelated provider domain does not satisfy DMARC.
- Record the source. Save the connecting IP, rDNS hostname, selector, signed domain, return-path, and campaign type in the authorized-sender inventory.
A fast end-to-end test is better than checking each DNS record in isolation because it also catches the wrong From domain, an inactive selector, and a return-path that was never applied to the campaign.
Email tester
Send a real email to this address. Suped shows a results button when the test is ready.
?/43tests passed
Send a real TailoredMail message to the address generated by the tester. Review the full diagnosis only after TailoredMail has completed delivery, and repeat the test for each distinct From domain or sending configuration.
SPF and DKIM should both pass when fully configured, but DMARC requires one aligned pass. If TailoredMail ever uses a stream that cannot apply your custom return-path, SPF alignment errors are expected and acceptable only when aligned DKIM consistently passes.
|
|
|
|---|---|---|
From | Your domain | Fix sender identity |
SPF | Pass with aligned smtp.mailfrom | Check return-path |
DKIM | Pass with aligned d= | Check selector |
DMARC | Pass | Fix alignment |
rDNS | Corroborated source | Confirm source; rDNS is not a DMARC pass condition |
Expected TailoredMail authentication signals
SPF passes but DMARC fails
- Compare domains. The return-path probably uses a TailoredMail-owned domain that does not match the From domain under DMARC alignment.
- Fix the path. Apply the custom return-path or rely on a verified aligned DKIM signature.
DKIM passes and DMARC passes
- Accept the result. DMARC is satisfied when the DKIM d= domain aligns with the From domain.
- Investigate SPF separately. A forwarding path can break SPF without invalidating the aligned DKIM result.
When the result still fails, send TailoredMail the full raw headers and identify the expected From domain, selector, and return-path. A cropped screenshot hides the identifiers needed to diagnose alignment.
Monitor TailoredMail authentication failures
A passing test is only a snapshot. DNS edits, TailoredMail selector rotation, a changed return-path, or a new campaign stream can break alignment later. Suped, our DMARC platform, provides DMARC monitoring that groups aggregate reports by sending source and highlights authentication failures.
Add the reporting address Suped assigns to rua, verify TailoredMail as an approved source, and set failure alerts for the domain. This keeps authentication changes visible without reviewing raw XML files.
Aggregate reports normally arrive daily, as described in RFC 9990. Alerts depend on report delivery and processing, so use live-message tests to check an immediate repair.
- Ingest reports. Add the address Suped assigns to rua without deleting existing required destinations, then wait for receiver reports to cover normal TailoredMail campaign volume.
- Verify the source. Mark the confirmed TailoredMail source only after its IP, rDNS, DKIM domain, and return-path match a message you sent.
- Turn on alerts. Set failure thresholds and weekly summaries so reported SPF, DKIM, or alignment failures reach the responsible owner.
- Use guided fixes. Follow Suped's automated issue detection and source-specific steps, then verify the repair against fresh report data.
- Watch related risk. If authentication passes but delivery still changes, review blocklist (blacklist) status separately. A DMARC pass does not guarantee inbox placement.
Alert on change, not only total failure
A new unverified TailoredMail source or a sharp drop in aligned pass rate deserves review before DMARC reaches zero. Suped separates verified and unverified sources, shows the failing mechanism, and keeps the repair tied to the affected stream.
Keep alerts assigned to a person who can change both TailoredMail and DNS. Authentication incidents linger when the platform owner can see the campaign but the DNS owner cannot see the failed selector or return-path.
Secure your domain with p=reject
Move to p=reject only after TailoredMail and every other legitimate sender is identified and consistently passes DMARC. Use a complete business sending cycle, including scheduled newsletters, automations, and low-frequency transactional messages, as the evidence window.
DMARC enforcement path
Advance only when authorized sources remain aligned and unexplained volume has been investigated.
Observe
p=none
Inventory TailoredMail and every other sender.
Quarantine
p=quarantine
Request spam handling for DMARC-failing mail.
Reject
p=reject
Request rejection of DMARC-failing mail.
- Build the inventory. Classify every source in DMARC reports. Match TailoredMail with a known campaign and investigate every unknown source before enforcement.
- Require aligned DKIM. Make custom DKIM the baseline for TailoredMail. Keep aligned SPF as a second path where the custom return-path is supported.
- Cover rare traffic. Wait through invoice notices, annual messages, triggered campaigns, and other low-frequency traffic before judging the inventory complete.
- Stage quarantine. Apply p=quarantine only after legitimate sending is verified, then review fresh reports before p=reject. Treat the policy as applying to all DMARC-failing mail in scope.
- Publish reject. Change to p=reject after authorized mail continues to pass DMARC under quarantine. Continue alerts because new senders and DNS changes still occur.
RFC 9989 removed pct percentage sampling. Do not rely on pct=25 to limit enforcement. The t tag requests test mode rather than sampling; older receivers can ignore it. The following values are successive stages, not separate records to publish together.
Staged DMARC policy valuesdns
v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com v=DMARC1; p=reject; rua=mailto:dmarc@example.com
Suped's Hosted DMARC lets the domain owner manage policy after publishing the assigned CNAME delegation. Review source verification and fresh reports in Suped before each policy change. Replace the existing DMARC TXT record during delegation; do not leave TXT and CNAME records at the same hostname.
Do not downgrade an enforced domain
If the domain already has p=quarantine or p=reject, keep it. Authenticate TailoredMail before broad production use, test a controlled message, and fix the sending identity instead of returning the whole domain to p=none.
After p=reject is active, review every TailoredMail configuration change as an authentication change. A new From domain, return-path, selector, account, or sending pool needs another live test and fresh DMARC evidence.
TailoredMail authentication FAQ
Yes. TailoredMail advertises SPF, DKIM, and DMARC support alongside custom domains. Request the exact DNS values and supported custom identities from your account manager. TailoredMail configures its sending authentication; the domain owner still publishes the DMARC policy and confirms a live message passes.
TailoredMail is the likely sending platform when a connecting host has an rDNS name under tailoredmail.com or tailorednews.com. Confirm it by matching the IP, return-path, DKIM d= domain, and a campaign you sent. An rDNS suffix is supporting evidence, not authentication by itself.
No. DMARC passes when either SPF passes with an aligned return-path or DKIM passes with an aligned signing domain. Configure both where available, and make aligned DKIM the dependable path for forwarded mail.
The SPF-authenticated return-path probably does not match the visible From domain under DMARC alignment. Apply the custom TailoredMail return-path under your domain or enable custom DKIM with an aligned d= domain, then retest a new message.
Yes, when no enforcement policy already applies, including inherited subdomain policy. Use p=none to collect reports and identify legitimate sources, then test quarantine before p=reject without relying on pct sampling. Keep existing quarantine or reject protection while authenticating TailoredMail.

