Send WordPress email through MailerSend
Connect WordPress to MailerSend through NimblyMail SMTP for modern deliverability tooling, templates, and per-domain SMTP credentials.
Why pair MailerSend with NimblyMail
MailerSend is a modern transactional email platform built by the team behind MailerLite, with a clean API, drag-and-drop template editor, and per-domain SMTP relay credentials. NimblyMail SMTP connects your WordPress or WooCommerce site to MailerSend so system emails go out through dedicated sending infrastructure, with delivery analytics available the moment you start sending.
MailerSend issues SMTP credentials per sending domain, separate from its API tokens — a clean separation that keeps your WordPress site’s relay access scoped to exactly one domain. Its dashboard gives you activity logs, bounce classification, and open/click tracking without extra configuration, which is useful for diagnosing WooCommerce email issues without digging through server logs.
MailerSend also supports TLS 1.2/1.3 on its relay and a modern template system, so if you later want branded HTML templates managed outside your WordPress theme, MailerSend’s editor is available without needing a second email service.
Connect MailerSend in three steps
Generate domain SMTP credentials
In MailerSend, go to Domains, select your sending domain (add one if needed), and open the SMTP tab to generate SMTP credentials for that domain.
Configure NimblyMail
In WordPress, go to NimblyMail SMTP > Settings, select MailerSend, and enter host smtp.mailersend.net with port 587 (STARTTLS), then enter the domain-specific SMTP username and password from step 1.
Send a test email
Send a test email from NimblyMail to confirm the connection authenticates and mail is delivered.
MailerSend requires domain verification before it will relay mail from that domain. Under Domains > [your domain] > DNS Records, add the SPF TXT record, DKIM TXT record, and return-path CNAME MailerSend provides, then click Verify in the MailerSend dashboard — unverified domains cannot send.
MailerSend + WordPress, answered
MailerSend's free allowance has changed over time and is currently limited (well under previous levels); check MailerSend's current pricing page for the exact free-tier cap before relying on it for production volume.
No — MailerSend issues separate SMTP username/password pairs per domain, distinct from API tokens used for its HTTP API. NimblyMail SMTP needs the SMTP credentials, not the API token.
The domain must show as verified/active in MailerSend's dashboard — unverified or pending domains will reject SMTP authentication even with correct credentials.
NimblyMail sends the HTML your WordPress site generates; MailerSend's built-in template editor is a separate feature for emails you compose and trigger directly through MailerSend's own API, not something WordPress automatically pulls in.
MailerSend's infrastructure details (including any regional options) are best confirmed on their current documentation, as hosting regions can change.
More integrations
View all integrations
SMTP.com
ProConnect WordPress to SMTP.com through NimblyMail SMTP for established, enterprise-grade transactional email delivery.
Setup guide
Mailgun
ProConnect WordPress to Mailgun with NimblyMail SMTP for reliable delivery, built-in email validation, and full send logs in wp-admin.
Setup guide
Brevo (Sendinblue)
FreeAPI key authentication, a generous free tier, and a platform that handles both transactional and marketing email.
Setup guide
Amazon SES
FreeIAM credentials, 19 regional endpoints, $0.10 per 1,000 emails. Lowest-cost transactional transport at volume.
Setup guide