AcelleMail + Amazon SES for maximum performance

Yes — SES is one of the sending drivers that ship in the box, alongside SendGrid, SparkPost, Mailgun, Elastic Email, Blastengine, Gmail relay, plain SMTP and more, plus a plugin SDK for anything not on that list. You can add several at once, route different lists through different providers, and move a campaign from one to another without touching your subscribers. Pointing AcelleMail at your own Postfix or Exim server works the same way.

Go to Sending Servers → Add and pick Amazon SES. You can connect with SES SMTP credentials or with API keys — either is fine. AcelleMail then generates the SPF and DKIM records for you to publish in DNS, and signs DKIM at the application layer. Run the built-in test send and you are live. The SES setup guide walks through it screen by screen.

Yes, automatically. AcelleMail ships a webhook endpoint for Amazon SES notifications delivered over SNS, so a hard bounce or a spam complaint is recorded against the subscriber and that address is suppressed from future sends. That suppression is what protects your sender reputation over the long run — re-sending to addresses that already bounced is the fastest way to lose it. The handler lives in app/SendingServers/Webhooks/ in the source, so you can extend it.

Yes. New AWS accounts start in the SES sandbox, where you can only send to addresses you have verified, at a low rate. Request production access from the SES console — it is usually granted within a day — and verify your sending domain. After that you can send to any recipient, up to your account quota. Everything on the AcelleMail side can be installed and configured while you wait.

AcelleMail is a one-time licence ($80 Regular / $199 Extended) with 1 year of point and minor updates and no recurring software fee. On top of that you pay AWS for what you send — roughly $0.10 per 1,000 emails — plus a modest VPS to run on. A sender doing 500,000 emails a month pays about $50 of SES. There is no per-subscriber pricing anywhere in the stack, so the size of your list never moves the bill.

Your ceiling is the SES quota on your AWS account, which AWS raises as your sending reputation builds. AcelleMail respects it: each sending server carries its own hourly and daily quota, and you can add several servers and let it rotate sending across them — useful when you run SES in more than one region, or SES alongside a second provider. The application itself is built for large lists; the practical limit is what AWS lets you send.

Whichever region you verified your domain in — AcelleMail asks for the region when you add the sending server, and the choice mainly affects the endpoint you send to. Domain verification, DKIM setup and sending quotas are per-region in SES, so if you later add a second region, verify the domain there too and add it as a separate sending server. Both can then run side by side.

Yes — that is the AcelleMail Extended License ($199). It adds a multi-tenant layer on top of a single SES account: customer accounts, subscription plans, six payment gateways (Stripe, PayPal, Braintree, Razorpay, Paystack, Offline), prorated upgrades, dunning and white-label branding. You run one install, your clients log in to their own accounts, and all sending flows through your AWS account. See For Developers.