Newsletter Plugins That Send via Amazon SES for Near-Zero Cost
Email service providers charge for the size of your list. Amazon SES charges for the emails you actually send, at a fraction of a cent each. Those two models produce numbers that are not in the same league once a list passes a few thousand people, and the gap only widens.
What makes SES a real option rather than a theoretical one is a small set of WordPress plugins that handle the sending, the queueing and, crucially, the bounce and complaint handling that SES requires you to take seriously. This article models the cost at three list sizes, names the plugins that make it practical, and is honest about the point where the setup burden stops being worth the saving.
Verified August 2026. Cloud sending rates and plugin prices change; treat the figures here as the shape of the comparison and price your own volume before committing.
Per subscriber versus per email
The distinction sounds like pricing trivia and is actually the whole article, because the two models scale completely differently with the same list.
Per-subscriber pricing charges for storage, not activity. A subscriber who never opens anything costs the same as your best customer. If you email monthly, you pay the same as somebody emailing daily. Inactive subscribers are pure cost, which is why every ESP guide eventually tells you to prune your list.
Per-email pricing charges for what you do. A dormant subscriber costs nothing until you email them. Send twice a month instead of four times and your bill halves. The list can grow to any size and cost nothing until you use it.
Model it. At 5,000 subscribers emailing weekly, that is 20,000 emails a month; SES-style pricing puts that in single-digit dollars, while ESP plans at that list size typically run tens of dollars a month. Real but not dramatic.
At 20,000 subscribers emailing weekly, 80,000 emails a month lands in the region of ten dollars of sending, against ESP plans commonly well over a hundred a month. Now you are looking at a four-figure annual difference, which is where the migration starts to justify itself.
At 100,000 subscribers, 400,000 emails a month is perhaps forty dollars of sending against ESP pricing in the several hundreds monthly. The gap over five years funds a considerable amount of engineering time, and this is the band where nearly everyone who can self-host does.
The 6 options compared
1. Mailster
The plugin most obviously built for high-volume self-hosted sending, and the one whose architecture assumes you will be pushing serious numbers.
Its queue and cron handling is the part that matters. Sending 80,000 emails is not one operation, it is thousands of small batches spread over hours, with retry logic when a batch fails and rate limiting so you stay inside your sending quota. Get that wrong and you either exceed your allowance or your emails trickle out over three days. Mailster treats this as a first-class concern rather than an afterthought, supports SES natively, and handles bounces properly. It is sold as a one-time licence, which pairs neatly with per-email sending: both your plugin and your delivery stop being monthly costs. The trade-off is that it is a more technical product than the friendly newsletter plugins, and it expects you to understand what a bounce rate is.
- SES support: Native, first-class
- Bounce handling: Yes, properly implemented
- Best for: Lists above 20,000 sending regularly
- Watch out for: Assumes technical competence
2. FluentCRM
The best fit when the list is a customer base rather than an audience. $103, $199 and $399 a year, priced by site with no per-contact fees at all.
That pricing model is the point: a plugin that charges by site combined with sending that charges by email means your costs are almost entirely decoupled from list size. Add 50,000 contacts and neither number moves much. On top of that you get segmentation, tagging, automation sequences and contact histories, which is a genuinely different product from a newsletter sender. It connects to SES through a transactional sending plugin rather than natively, which is one more component but a well-trodden one. For a membership site, a course business or a store where you want behaviour-triggered email without per-contact billing, this is the strongest combination available.
- SES support: Via a transactional sending plugin
- Bounce handling: Yes, with the right connector
- Best for: Customer lists needing automation
- Watch out for: One more component in the chain
3. The Newsletter Plugin
The long-standing free option with no subscriber cap, which makes it the cheapest genuine entry point to this approach.
Because you bring your own sending, there is no reason for the plugin to limit your list, and it does not. A blogger with 30,000 subscribers can run this at zero plugin cost and pay only for delivery, which is the purest expression of the per-email model. Its interface shows its age and the composer is not what you would choose if aesthetics mattered most, but the sending mechanics are sound and it has been maintained through many years of WordPress changes. Paid add-ons extend it where needed. For somebody whose priority is a large list at minimum cost and who does not need automation, this is very hard to beat.
- SES support: Yes, via SMTP or add-on
- Bounce handling: Add-on dependent
- Best for: Large lists on a zero plugin budget
- Watch out for: Dated interface and composer
4. MailPoet
The friendliest product here, and the one whose own pricing runs against the argument. Free to 500 subscribers and 5,000 emails a month, with Business plans from around $10 a month scaling with list size.
Its composer is the best of the group and the WooCommerce integration is the deepest, so for a store owner who wants abandoned-cart and post-purchase emails without becoming an email engineer, it is an easy recommendation. You can point it at your own SES credentials rather than its bundled sending service, which keeps the cheap delivery while retaining the pleasant interface. But the plugin subscription itself scales with subscribers, so you are only removing one of the two per-subscriber costs. If your reason for reading this article is a 40,000-person list, the arithmetic will push you toward the flat-priced alternatives. If it is a 3,000-person store list and you value your time, this is a reasonable place to stop.
- SES support: Yes, with your own credentials
- Bounce handling: Yes
- Best for: Stores under a few thousand subscribers
- Watch out for: Plugin price still scales with list size
5. FluentSMTP as the delivery layer
Not a newsletter plugin, but the component that makes several of the others work, and completely free including logging.
Its job is to take every email WordPress generates and route it through a proper sending service instead of the server mail function, with SES among the supported connections. That gives you delivery logging, retry on failure and the ability to route different kinds of mail through different services, which is more than most paid transactional plugins offer. The routing capability is genuinely useful: send your newsletter through SES for cost, and your password resets through a different provider so a sending pause on one never blocks the other. Since it costs nothing and improves deliverability for the whole site rather than just campaigns, there is no real argument against installing it regardless of which newsletter plugin you choose.
- SES support: Yes, plus routing by mail type
- Bounce handling: Logging and retry included
- Best for: Every site, alongside a newsletter plugin
- Watch out for: It sends, it does not manage campaigns
6. Staying with an ESP
The comparison point, and the right answer more often than a cost-focused article usually admits.
What the monthly fee buys is not software, it is reputation management. The provider maintains relationships with inbox providers, monitors their own sending pools, handles blocklist removal, and employs people whose job is making sure mail arrives. Move to SES and all of that becomes yours: your sending reputation, your bounce rate, your problem when a large provider starts filtering you. The provider also gives you deliverability reporting, template design, support you can shout at, and the confidence that comes from somebody else being accountable. If email is a primary revenue channel and you do not have somebody comfortable reading bounce logs, the fee is cheap insurance. The saving is real, but it is a saving purchased with responsibility.
- SES support: Not applicable, they run their own
- Bounce handling: Theirs, with reputation management
- Best for: Email as a primary revenue channel
- Watch out for: Cost scales with list size permanently
Comparison table
| Option | Plugin cost | Scales with list | SES support | Automation |
|---|---|---|---|---|
| Mailster | One-time licence | No | Native | Basic |
| FluentCRM | $103/yr per site | No | Via connector | Strong |
| The Newsletter Plugin | Free | No | Yes | Limited |
| MailPoet | From $10/mo | Yes | Yes | Good |
| FluentSMTP | Free | No | Yes, routing | Not applicable |
| ESP | Monthly, by size | Yes | Not applicable | Strong |
What SES demands in return
The cheap sending comes with obligations, and skipping any of them turns the saving into a deliverability problem that is much more expensive than the fee you avoided.
- Verify your domain and publish the authentication records. Domain verification, sender authentication and a policy record are all required for mail to be trusted. Send without them and you will land in spam folders regardless of content quality.
- You start in a sandbox. New accounts can only send to verified addresses until you request production access, and that request asks how you collected your list and how you handle unsubscribes. Have honest answers ready.
- Warm up gradually. A brand new sending identity blasting 50,000 emails on day one looks exactly like a compromised account. Increase volume over two to three weeks, starting with your most engaged subscribers.
- Bounce and complaint handling is mandatory, not optional. You must process bounces and remove those addresses automatically. Ignore this and your account gets suspended, which is the failure mode that catches people out.
- Watch your complaint rate closely. Spam complaints above a fraction of a percent put your account at risk. Prune inactive subscribers and make unsubscribing genuinely easy, because an unsubscribe is far cheaper than a complaint.
- Sending 80,000 emails needs real cron. The default WordPress scheduler fires on page visits, which is unreliable for a task running for hours. Set up a system cron job hitting the scheduler on a fixed interval.
None of this is difficult, but all of it is your responsibility now. Budget a day for the initial setup and a couple of hours a month watching the numbers, and be honest about whether that time is worth the saving at your list size.
Frequently asked questions
How much cheaper is SES really?
At 20,000 subscribers emailing weekly, sending costs are typically around ten dollars a month against ESP plans well into three figures. The gap widens with list size.
At what list size is it worth switching?
Below about 5,000 subscribers the saving rarely justifies the setup and monitoring. Between 5,000 and 20,000 it becomes arguable, and above that it is usually compelling.
Will my deliverability get worse?
It can, because sending reputation becomes yours. Authenticate your domain properly, warm up gradually and handle bounces automatically, and it holds up well.
Can my shared host send tens of thousands of emails?
The sending happens at the cloud provider, not on your server, so the load is modest. What your host must support is a reliable cron job to work through the queue.
Which plugin handles high volume best?
Mailster, because its queueing, batching and retry logic are designed for exactly this. FluentCRM is the better choice if you need segmentation and automation alongside.
What happens if I ignore bounces?
Your bounce rate rises, your sending reputation falls and the provider eventually suspends the account. Automatic bounce processing is a requirement, not a refinement.
The verdict
Above 20,000 subscribers the arithmetic is decisive, and Mailster is the plugin built for it. Its queueing and bounce handling are what separate a send that completes overnight from one that trickles out for three days.
If the list is customers rather than readers: FluentCRM at $103 a year, priced per site with no per-contact fees, which decouples your bill from your list entirely.
On a zero budget with a large list: The Newsletter Plugin, free with no subscriber cap, paying only for delivery.
Below about 5,000 subscribers, do not bother. The saving is small, the setup is a day, and the ongoing responsibility for your own sending reputation is a poor trade for a few dollars a month. Install FluentSMTP for free anyway; it improves every email your site sends.
