MailPoet is a full email marketing and newsletter platform for WordPress – drag-and-drop email builder, subscriber management, automated campaigns, WooCommerce integration – that ships with its own sending infrastructure called the MailPoet Sending Service. The plugin has 500,000+ active installs, is maintained by Automattic (the company behind WordPress.com and WooCommerce), and has operated since 2011. The sending service is optimised for delivering MailPoet’s own newsletter and marketing sends and does not present itself as a standalone transactional SMTP relay.
That shape sorts the two common WordPress email jobs cleanly. Sites building newsletters and marketing automation from inside WordPress reach for MailPoet, and let its sending service handle delivery so a separate relay is not needed for those campaigns. Sites whose primary need is transactional delivery through wp_mail() – password resets, form notifications, order receipts – reach for a standard mailer plugin (WP Mail SMTP, FluentSMTP, Post SMTP) paired with a dedicated relay (SMTP2GO, Postmark, Brevo). Sites that need both run MailPoet for newsletters alongside a mailer + relay stack for transactional traffic.
What the MailPoet Sending Service does well
The MailPoet Sending Service is the delivery infrastructure behind MailPoet’s own newsletter and marketing email. It is built around the operational jobs a newsletter platform needs, and handles those jobs without asking the site owner to wire them up:
- Campaigns and automation designed in the MailPoet editor: newsletters, welcome sequences, post notifications, WooCommerce abandoned-cart and post-purchase flows.
- List hygiene handled automatically: undeliverable addresses are pulled out of the list on bounce, and complaints route the same way, without a webhook to configure.
- One-click List-Unsubscribe on every campaign, which is what Gmail and Yahoo’s bulk-sender rules require for anyone sending 5,000 or more messages a day to consumer inboxes.
- WooCommerce campaign hooks that read live from the store: send thank-yous after purchase, encourage repeat orders with a discount, or recommend complementary products based on cart history.
The service does not replace wp_mail() for plugins outside MailPoet’s scope. A contact form plugin, a membership plugin, or WordPress core password reset emails are not routed through the MailPoet Sending Service unless you configure MailPoet to intercept all site email. Doing so is supported, but it sits outside what the service is designed for: a newsletter platform picking up transactional traffic, not a transactional relay optimised for it.
Pricing
MailPoet’s pricing is based on subscriber count, not email volume (except on the free tier):
| Plan | Price | Subscribers | Sending | Notes |
|---|---|---|---|---|
| Starter | Free | Up to 500 | 5,000/mo via MailPoet service | MailPoet branding in emails |
| Creator | From $8/mo (500 subs) | Scales | Your own sending method | Premium features, no MailPoet Sending Service |
| Business | From $10/mo (500 subs) | Scales | Unlimited via MailPoet service | Premium features + sending |
| Agency | From $30/mo (500 subs) | Scales | Unlimited via MailPoet service | Up to 50 sites |
The free Starter plan (500 subscribers, 5,000 emails/month) includes the MailPoet Sending Service – no external relay needed for newsletter delivery at this scale. The MailPoet branding on free-tier emails is the trade-off.
For context on transactional-only needs: the Starter plan’s 5,000 emails/month sounds generous, but it covers newsletter sends too. A site with 400 subscribers sending a weekly newsletter uses ~1,600 of those emails on campaigns alone, leaving ~3,400 for transactional. SMTP2GO offers 1,000 transactional emails/month free with no subscriber cap, no branding, and no newsletter platform bundled in – a better fit when transactional is the only job.
Free tier
MailPoet’s Starter plan is permanent – up to 500 subscribers and 5,000 emails/month delivered via the MailPoet Sending Service, MailPoet’s own delivery infrastructure. No external SMTP relay to configure and no additional signup; installing MailPoet is the whole setup.
The catch to notice first: MailPoet branding appears in the footer of every free-tier email. Every newsletter, welcome sequence, and WooCommerce transactional message MailPoet handles carries a “sent by MailPoet” line at the bottom. Paid tiers (Creator $8, Business $10, Agency $30 at 500 subs, all monthly) remove the branding and unlock premium features; the Business and Agency tiers include unlimited sending via the MailPoet Sending Service.
The exclusions are architectural rather than featured. MailPoet is not a general-purpose transactional relay: contact-form plugins, membership plugins, and core WordPress password resets do not flow through MailPoet unless you configure MailPoet to intercept all site email, and even then MailPoet is a newsletter plugin doing a side job rather than a purpose-built relay doing its primary one. No delivery webhooks, no dedicated IP, no email validation API, no inbound routing. Log retention is minimal and not documented in the way transactional relays document it.
The 5,000/month allowance also has to cover newsletter sends. A site with 400 subscribers sending a weekly newsletter uses roughly 1,600 emails on campaigns alone; that leaves 3,400 for automated sequences and any WordPress transactional traffic MailPoet is routing.
The tier fits a small WordPress site running newsletters and marketing automation from inside WordPress at low list size, especially when the site owner already accepts a plugin-managed email stack. It does not fit a site whose primary email need is transactional; that site should install a mailer plugin (WP Mail SMTP, FluentSMTP) with a dedicated relay (SMTP2GO, Postmark) and keep MailPoet for newsletters only if newsletters are part of the plan.
Verdict
MailPoet fits WordPress sites that run newsletters and marketing automation from inside WordPress, where the team managing the site also manages the list. The Starter tier (up to 500 subscribers, 5,000 emails/month via the MailPoet Sending Service) covers small newsletter operations without a separate SMTP account to configure or maintain. Automattic ownership, a June 2026 release, and a 500K+ install base put it among the more stable options in the WordPress newsletter category.
Sites whose primary email need is transactional – password resets, form submissions, admin notifications, order receipts – are usually better served by a standard mailer plugin (WP Mail SMTP, FluentSMTP, Post SMTP) connected to a dedicated relay (SMTP2GO, Postmark, Brevo). Installing MailPoet purely for transactional delivery brings in a newsletter builder, subscriber manager, and automation editor that that site will not use.
Sites that need both a subscriber newsletter and reliable wp_mail() traffic can run both cleanly: MailPoet on its own sending service for newsletters, a mailer plugin plus a dedicated relay for transactional. The two paths do not interfere with each other, and this split is the recommended configuration for that shape of site.
Plugin data from wordpress.org (v5.30.0, June 2026, 500K+ installs). Plan details from MailPoet Knowledge Base.