Send WordPress email through Postmark
Send fast, reliable WordPress transactional email through Postmark with NimblyMail SMTP — simple token auth and industry-leading delivery speed.
Why pair Postmark with NimblyMail
Postmark is built exclusively for transactional email — no marketing-blast infrastructure competing for the same sending reputation — which is exactly the kind of mail WordPress and WooCommerce generate. NimblyMail SMTP connects your site to Postmark’s servers using a single Server API Token, giving you some of the fastest, most reliable delivery available for order confirmations, password resets, and admin notifications.
Postmark’s entire product is optimized around one thing: getting a single transactional message into an inbox as fast as possible. Because Postmark doesn’t send bulk marketing campaigns from the same infrastructure, its shared IP reputation stays clean, which independent deliverability tests consistently show translates into some of the best inbox placement rates in the industry.
Authentication is unusually simple — one Server API Token acts as both the SMTP username and password, so there’s less to misconfigure. Postmark’s message streams also separate transactional and broadcast mail internally (useful if you later add a newsletter stream), though both draw from the same monthly sending allowance.
Connect Postmark in three steps
Copy your Server API Token
In Postmark, create (or open) a Server, then copy its Server API Token from the server's API Tokens tab.
Configure NimblyMail
In WordPress, go to NimblyMail SMTP > Settings, select Postmark, and enter host smtp.postmarkapp.com with port 587 (STARTTLS). Use the Server API Token from step 1 as both the SMTP username and password.
Verify sender and test
Add and confirm a Sender Signature (or verify your full domain) in Postmark for the "From" address you'll use, then send a test email from NimblyMail to confirm it arrives.
Postmark requires a verified Sender Signature at minimum, but for the best deliverability, verify your full domain under Sender Signatures > Domains: add the provided DKIM TXT record and a Return-Path CNAME to your DNS zone. Domain verification also unlocks a custom Return-Path, which improves how mailbox providers score your messages.
Postmark + WordPress, answered
Yes — every new account gets a permanent free tier capped at 100 emails/month, which is enough to fully test your NimblyMail connection before committing to a paid plan.
Postmark is designed for transactional email; its acceptable use policy restricts bulk marketing sends on the transactional stream. Use a dedicated marketing platform for newsletters instead.
Servers let you separate API tokens and sending activity by project or environment (e.g., staging vs. production) — for most WordPress sites, one server is sufficient.
The From address in NimblyMail's settings must exactly match a verified Sender Signature or a verified domain in Postmark — mismatches are the most common setup error.
Paid plans start around 10,000 emails/month, billed with per-thousand overage rates if you exceed your plan — check Postmark's current pricing page for exact figures before committing to a tier.
More integrations
View all integrationsSendGrid
ProRoute WordPress and WooCommerce email through SendGrid using NimblyMail SMTP — fast setup, API key auth, and delivery tracking.
Setup guideMicrosoft 365 / Outlook
FreeConnect your Microsoft 365 account via OAuth 2.0 and send WordPress emails through Outlook or Office 365.
Setup guideZeptoMail
FreeZoho's transactional email API with five regional endpoints. Natural fit if your stack already includes Zoho One.
Setup guideMailjet
ProConnect WordPress to Mailjet via NimblyMail SMTP for EU-hosted, GDPR-friendly transactional email delivery from Sinch.
Setup guide