263 Enterprise Mail: MX, SPF, DKIM & DMARC Setup
Configure 263 Enterprise Mail on a custom domain: mxw.263.net at priority 5, mx.263.net at 10, the spf.263.net include, DKIM generated in the admin console, and DMARC reporting.
Aliyun Mail & DirectMail: DKIM, SPF & DMARC Setup
Step-by-step Aliyun DirectMail sender domain verification: the six DNS records, the SPF include values, region-based DKIM selectors and DMARC publishing.
Alibaba Mail (Alimail) SPF, DKIM & DMARC Setup Guide
Configure Alibaba Mail / Aliyun Enterprise Mail on your own domain: mx1-mx3.qiye.aliyun.com, the spf.qiye.aliyun.com include, default._domainkey DKIM and a DMARC record.
Postmark DKIM & Sender Signatures: Setup and Key Rotation
Postmark is a transactional email provider, and transactional mail — password resets, receipts, invoices — is exactly what you cannot afford to lose to a spam folder. Postmark handles most of the authentication design through its Sender Signatures: for each sending domain it generates a 2048-bit DKIM key and a Return-Path record, and once your DNS is confirmed, messages are signed with your domain and pass DMARC alignment.
What most teams get wrong is not the setup — it is rotation. This guide covers both: creating the signature, publishing records, and rotating keys without a single unsigned message going out.
What you need
- A Postmark account with access to Sender Signatures.
- DNS access to the domain (or subdomain) you send transactional mail from.
- A sending subdomain decision. A dedicated subdomain such as mail.yourdomain.com keeps transactional reputation separate from everything else on the root.
Configuration steps
- Open Sender Signatures, click Add Domain or Signature, and enter your sending domain — ideally a subdomain like mail.yourdomain.com.
- Postmark generates the DNS records for the signature. Two records do the work:
TXT 2026xxxx._domainkey.mail.yourdomain.com -> v=DKIM1; k=rsa; p=<2048-bit public key>
CNAME pm-bounces.mail.yourdomain.com -> pm.mtasv.net
The DKIM TXT hosts the public key (the selector before _domainkey is generated by Postmark — copy it exactly). The second is the Return-Path CNAME. Postmark marks it optional; publish it anyway: with it, the envelope sender becomes a subdomain of your domain, so SPF at the Return-Path both passes and aligns. Without it, mail goes out on Postmark's bounce domain and DKIM becomes your only aligned mechanism.
- Publish both records, then click Verify in Postmark. Verification usually completes within minutes; if it stays pending, check that the DKIM TXT value has no inserted line breaks and the CNAME target is exactly pm.mtasv.net — the record in your own account is authoritative.
- Once the signature shows DKIM and Return-Path as verified, send transactional mail from any address on that domain.
Postmark does not require an SPF record on your sending domain: SPF is evaluated at the Return-Path domain, which the CNAME covers. If your inventory expects an SPF include anyway, the documented value is spf.mtasv.net — do not add it to the root record unless needed, since it consumes one of your ten SPF lookups.
Key rotation
Rotate DKIM keys periodically — once a year is a reasonable default. Postmark can issue a new 2048-bit key for a signature: request it from the signature's settings or from support (the Domains API exposes the same operation). The new key uses a different selector, which makes zero-downtime rotation possible:
- Request the new key. Postmark provides a new DKIM TXT record with a new selector.
- Publish the new TXT record alongside the old — both selectors coexist in DNS; receivers query whichever one a message references.
- Verify the new selector first — confirm the record resolves with the TXT Lookup tool and that a test message passes DKIM in the Email Header Analyzer.
- Keep the old record for one to two weeks so in-flight messages still verify, then remove it from DNS.
Never delete the old selector's record on the day the new key starts signing — mail in transit still references the old public key.
Verify
Send a test message to Gmail and open Show original: DKIM should pass with d=mail.yourdomain.com, SPF with the pm-bounces subdomain, and DMARC overall. Cross-check with the DKIM Checker (your domain plus the selector from the record host) and the Email Health Check. For the concepts, see the authentication fundamentals guide.
Common mistakes
- Skipping the Return-Path CNAME because it is optional. Without it you rely solely on DKIM alignment — fragile when receivers tighten checks.
- Using the root domain for everything. Transactional and marketing mail on one domain ties their reputations together. Use a subdomain per mail type.
- Deleting the old DKIM record immediately after rotation. In-flight messages signed with the old selector fail verification. Keep the old record one to two weeks.
- Splitting the DKIM TXT value. Some DNS panels insert line breaks into long values, corrupting the public key. If verification fails on a correctly copied key, inspect the stored record with the TXT Lookup tool.
- Creating an SPF record Postmark never asked for. Adding an include at your root domain is unnecessary and burns one of your ten SPF lookups.
Frequently asked questions
What is the difference between a sender signature and a domain?
Each domain you add gets a signature with its own DKIM key and Return-Path records; Sender Signatures is where you manage them. A single-address signature is possible, but domain-level signatures are the right choice for DMARC alignment.
How often should I rotate DKIM keys?
No hard rule — annual is a sensible default, some policies require more. What matters is the selector overlap: no signed message should reference a key missing from DNS.
Can Postmark sign with my own key?
No. Postmark generates and holds the 2048-bit key pair; you publish the public key. For full key custody, a bring-your-own-key option such as Amazon SES BYODKIM is the better fit — see the Amazon SES authentication guide.
Does Postmark pass Gmail and Yahoo sender requirements?
Once the signature is verified, yes: SPF, DKIM and DMARC all pass with alignment. The requirements also cover one-click unsubscribe and complaint rates, which depend on how you send — see the basics guide.
Related Tools
Need Help?
Our tools are designed to be intuitive, but if you need assistance, we're here to help.
About Our Tools
Professional-grade email and DNS diagnostic tools trusted by IT professionals worldwide.
