How to send 50,000 emails per month for under $5 with AcelleMail + Amazon SES

"Self-hosted is cheaper than SaaS at 50K subscribers" is the standing argument on /guide/email-marketing-cost-savings. The pillar guide handles the long-form math at multiple list sizes; this post zooms in on the most-asked single number: 50,000 messages per month — a typical small-to-mid newsletter or SaaS lifecycle volume.

The breakdown into recurring monthly cost:

So strictly the SES line is under $5 at 50K (current AWS pricing); the all-in is $18-22 if you also need the EC2 host. The "$5" claim refers specifically to the marginal cost of sending — what your sending volume costs, on top of fixed infrastructure you may already be running. Verify the current SES rate on aws.amazon.com/ses/pricing before quoting. Outbound data transfer costs are charged separately and depend on region.

Three common patterns push the cost above the headline number:

1. Sandbox-to-production gap. SES new accounts start in sandbox (200 messages/day, manually verified recipients only). Leaving sandbox is a free request via the SES console — describe your use case, list-hygiene practices, bounce-handling plan. Approval is typically within 24h. Skipping this step keeps you stuck at the sandbox cap regardless of price.
2. Region selection. SES pricing is region-specific. If your subscribers are concentrated in a region, send from that region to minimise both latency and data-transfer cost. The pricing page lists rates per region.
3. Rich attachments. SES bills extra per GB of data sent above a free tier per message. For text-only newsletters this is negligible; for PDF / image-heavy transactional mail it can dominate at high volumes. The fix is to host attachments on your CDN and link to them rather than attach.

The installation walks the standard LEMP path:

The web installer takes seven steps: license validation, DB credentials, mail-from defaults, admin account, SES credentials (or any other vendor), cron-config check, and a final settings sweep. The whole thing is well under 10 minutes if you have the AWS access keys handy.

If you do not want to run your own EC2 host, you can also install AcelleMail on shared hosting (cPanel, Plesk, or any LAMP/LEMP host with PHP 8.3 + MySQL 8) — the cost line then collapses entirely into your existing hosting bill.

In AcelleMail admin, Sending servers → Add sending server → Amazon SES → SMTP. AcelleMail ships three SES drivers under app/SendingServers/Drivers/Vendors/Amazon/: AmazonBaseDriver.php (shared), AmazonSmtpDriver.php (SMTP transport), and AmazonApiDriver.php (HTTPS REST). For new operators the SMTP driver is recommended — it works without IAM-policy fiddling and is identical in deliverability to the API driver.

SES SMTP credentials are not the same as your AWS IAM access key. Generate them via SES console → "SMTP settings" → "Create SMTP credentials". This creates an IAM user with the minimal ses:SendRawEmail permission and exposes a username/password pair derived from that user's access key.

The full walkthrough is in The 7 DNS records every self-hosted email sender needs. The minimum to send via SES at 50K/month volume:

SES verifies the DKIM CNAMEs automatically once they propagate. You will see the verified status in the SES console under "Verified identities" within minutes of publishing.

SES production access is the gate between "200 messages/day to verified addresses" and "your account-level daily quota for whoever you want." The request form is short:

• Use case description. One paragraph — "I run a self-hosted newsletter for {audience} via AcelleMail; volume is ~50K/month."
• List-hygiene plan. Mention double opt-in, unsubscribe handling, complaint-feedback processing.
• Compliance with AUP. Tick the box.

AWS approval typically lands within 24 hours. The sandbox-to-production transition is the single most-skipped step new operators trip on; you can install AcelleMail, send fine to the verified test address, and then be confused when sending to real subscribers fails. Always check whether your account is in production access before debugging anything else.

If you are using SES with shared IPs (the default), you do not need to warm the IP — SES production IPs are pre-warmed pools and you inherit their reputation. What you do need to warm is the From-domain: even on a shared SES IP, mailbox providers track per-domain reputation, so a brand-new domain still goes through a 2-3 week ramp before reaching peak sending.

The standing schedule is in A 6-week IP warmup schedule. Compressed: start at 50/day, double cautiously, target 50K/month over 4-6 weeks. AcelleMail's WarmupStrategy model executes this automatically — configure it on the sending server and the per-day cap is enforced before any campaign runs.

Three places to watch:

• SES Reputation metrics (in the SES console). Bounce rate must stay under 5% (warn) / 10% (pause). Complaint rate must stay under 0.1% (warn) / 0.5% (pause). Practical working margin: bounce < 2%, complaints < 0.05%.
• Google Postmaster Tools (postmaster.google.com). Free; surfaces daily spam-rate, IP / domain reputation, authentication-pass rate, and feedback loop deliveries. Sign up the day you publish DNS, not later.
• AcelleMail Bounce / Complaint dashboard. The webhook receivers (app/SendingServers/Webhooks/BounceReceived.php + ComplaintReceived.php) consume SES SNS events and write rows to BounceLog; the admin dashboard graphs the rate over time. Hard bounces auto-blacklist; soft bounces accumulate.

Self-hosted at 50K/month is unambiguously cheaper than every SaaS option. But the cost-per-message advantage is not the only axis. Three situations where SaaS is the better choice regardless of price:

1. You have no operations bandwidth. SES + AcelleMail is low-effort but not zero-effort. SPF / DKIM / DMARC need eyes; warmup needs eyes; bounce-rate spikes need eyes. If "running a server" is not in your team, SaaS solves it for you in dollar terms.
2. Your audience is global with regional inbox-quirks. Naver in Korea, mail.ru in CIS, QQ in China — each has its own deliverability quirks. SaaS providers with regional presence handle this for you. Self-hosted means you handle it.
3. You need built-in advanced editor / template marketplace. AcelleMail has a builder and standard templates; the SaaS premium-tier ones are flashier. If your campaigns are visually intricate and the design tooling is the bottleneck, that is a SaaS-wins case.

For everyone else — the technical operator with a 50K-subscriber list and basic ops chops — the math works. The cost line is real and stable; the operational complexity is bounded; the deliverability is identical to SaaS once the seven DNS records are in place. The longer treatment lives in /guide/email-marketing-cost-savings.