If you’re running a content business on WordPress—memberships, course sales, paywalled newsletters—you’ve probably installed WP Mail SMTP, Easy WP SMTP, or Post SMTP to fix the “WordPress emails not sending” problem. These plugins work. But most solo operators configure them once and never check which emails are actually routing through which server.
The result: transactional emails like password resets, purchase confirmations, and login codes get sent through the same SMTP connection as your marketing broadcasts. That’s a deliverability risk, a compliance headache, and in some cases a direct violation of your ESP’s terms of service.
Why WordPress doesn’t care which emails are transactional
WordPress core uses a single function—wp_mail()—to send every outbound email. Plugin update notifications, comment moderation alerts, WooCommerce order confirmations, and member login links all call the same function. There’s no built-in distinction between transactional and promotional.
When you install WP Mail SMTP and point it at your marketing ESP—say, MailerLite or Brevo—you’ve just told WordPress to route everything through that SMTP endpoint. MailerLite’s terms explicitly prohibit sending transactional email through their marketing SMTP relay. Brevo allows it, but only if you’ve configured a dedicated transactional sender and separated your IP reputation.
Most operators skip that step. They plug in their SMTP credentials, see the test email arrive, and move on. Six months later, a member complains they’re not getting password reset emails. You check spam folders, then logs, then realize your marketing ESP flagged the reset email as suspicious because it came from a domain with no SPF record for transactional sending.
What actually breaks
The failure modes vary by ESP and plugin, but the common ones are:
- Rate limits. Marketing ESPs throttle SMTP connections differently than transactional providers. MailerLite’s SMTP relay allows 200 emails per hour on the free tier. If your site sends 50 comment notifications in an hour, you’ve used a quarter of your sending quota before your next broadcast even starts.
- IP reputation bleed. When you send password resets through the same IP pool as your newsletter, a spam complaint on one affects the other. Transactional emails have higher open rates and lower complaint rates—mixing them with promotional content drags both down.
- Logging and compliance gaps. Marketing platforms log email for segmentation and engagement tracking. Transactional platforms log for delivery confirmation and audit trails. Sending a purchase receipt through a marketing ESP means that email gets added to a subscriber’s engagement history, skewing your open-rate metrics and potentially violating GDPR’s purpose-limitation principle.
Postmark, which specializes in transactional email, charges $10 per 10,000 emails with no monthly fee. Their SMTP relay is configured specifically for password resets, receipts, and system notifications—high deliverability, minimal tracking, and logs built for compliance. If you’re sending fewer than 10,000 transactional emails a month, the cost is a rounding error compared to the risk of your members not receiving login codes.
How to split your sending in WP Mail SMTP
WP Mail SMTP Pro (the paid tier, starts at $49/year) includes a feature called “Email Log” and “Email Controls” that let you route specific email types through different SMTP configurations. The free version doesn’t support multiple SMTP accounts, so you’ll need either the Pro version or a separate plugin like Post SMTP (free, supports multiple mailers).
Here’s the setup for Post SMTP:
- Install Post SMTP from the WordPress plugin repository.
- Add your transactional SMTP credentials first—Postmark, Amazon SES, or Brevo’s transactional API. Set this as the default mailer.
- Under “Message” settings, enable “Additional SMTP Settings” and add your marketing SMTP credentials as a secondary mailer.
- In the “Email Log” settings, create a rule: if the email subject contains “password” or “reset” or “order,” route through the transactional mailer. Everything else goes through marketing.
Post SMTP’s rules engine uses regex, so you can get granular. If you’re running WooCommerce, you can route all emails where the sender address matches orders@yourdomain.com through transactional, and leave everything from newsletter@yourdomain.com on the marketing relay.
One overlooked detail: SPF and DKIM per sender
Even if you route emails correctly, your DNS records need to authorize both SMTP servers. If your transactional emails come from noreply@yourdomain.com and your newsletters come from hello@yourdomain.com, both domains need SPF records that include both Postmark’s and MailerLite’s sending IPs.
Most operators add one SPF record and assume it covers everything. It doesn’t. Each sending domain needs its own record, and if you’re using subdomains (mail.yourdomain.com vs. yourdomain.com), each subdomain needs separate DNS entries. Postmark’s onboarding checklist walks you through this. MailerLite’s does not—you have to dig into their documentation.
The fastest way to verify: send a test email from each SMTP connection, then check the raw email headers. Look for spf=pass and dkim=pass in the Authentication-Results field. If either shows softfail or none, your DNS isn’t configured correctly.
Want more tooling breakdowns like this? Subscribe to One Two Three Send—one article every morning, no fluff, no affiliate pressure.
Heads up — some links in this article are affiliate links. If you sign up through them, we may earn a small commission at no extra cost to you. We only recommend tools we use ourselves.