Send WordPress email through Elastic Email
Connect WordPress to Elastic Email with NimblyMail SMTP for budget-friendly, reliable delivery on both SMTP and API sending.
Why pair Elastic Email with NimblyMail
Elastic Email is a budget-conscious sending platform that supports both SMTP relay and HTTP API delivery, making it a solid fit for WordPress sites and WooCommerce stores that want reliable transactional email without enterprise pricing. NimblyMail SMTP connects to Elastic Email’s relay in a few fields, so you can start routing order notifications and password resets through dedicated infrastructure right away.
Elastic Email’s core appeal is cost — its per-email pricing at volume undercuts many competitors while still offering a real dashboard, suppression list management, and bounce/complaint handling that automatically protects your sender reputation. For smaller WooCommerce stores watching every line item, this matters: you get transactional-grade infrastructure without transactional-grade pricing.
Because Elastic Email supports SMTP natively (rather than API-only), NimblyMail’s connection is a standard host/port/username/password setup with no special translation layer — useful if you’re migrating from another SMTP-based provider and want a drop-in swap.
Connect Elastic Email in three steps
Get your SMTP credentials
In Elastic Email, go to Settings > SMTP/API, and either note your account email (used as the SMTP username) or generate a dedicated API key to use as your SMTP password.
Configure NimblyMail
In WordPress, go to NimblyMail SMTP > Settings, select Elastic Email, and enter host smtp.elasticemail.com with port 2525 (alternatives 25, 587, or 465 also work if your host blocks 2525). Enter your account email as the username and your API key as the password.
Send a test email
Send a test email from NimblyMail to confirm authentication and delivery.
Elastic Email requires domain verification (SPF and DKIM) for reliable delivery and to unlock full sending limits. Under Settings > Domains, add your sending domain, then add the TXT (SPF) and DKIM records Elastic Email provides to your DNS zone before verifying.
Elastic Email + WordPress, answered
The free tier caps sending fairly low (around 100 emails/day) — fine for testing and very small sites, but most WooCommerce stores will want a paid plan for headroom and full deliverability features.
Use a dedicated API key as the SMTP password rather than your account login password — it's easier to revoke and doesn't expose your Elastic Email account credentials.
Some hosts block ports 25 and 587 for outbound mail to prevent spam abuse; 2525 is commonly left open and works identically for Elastic Email's relay.
Yes, but they're tracked separately in the dashboard — make sure your account/domain is configured for transactional sending if that's your primary WordPress use case, to keep reputation isolated from any bulk campaigns.
Elastic Email queues or rejects mail beyond your plan's cap depending on account status — check current limits in your dashboard if you're seeing delayed WooCommerce order emails.
More integrations
View all integrations
Mailjet
ProConnect WordPress to Mailjet via NimblyMail SMTP for EU-hosted, GDPR-friendly transactional email delivery from Sinch.
Setup guide
SendLayer
FreeBuilt exclusively for transactional email. No marketing features — just delivery infrastructure for messages that must land.
Setup guide
SparkPost
ProConnect WordPress to SparkPost with NimblyMail SMTP for advanced deliverability analytics and predictive engagement insights.
Setup guide
Microsoft 365 / Outlook
FreeConnect your Microsoft 365 account via OAuth 2.0 and send WordPress emails through Outlook or Office 365.
Setup guide