Sending providers
Send through Amazon SES, the default, or one of ten other providers. Compare them, pick one, and see what the platform handles for you.
How sending works
newsletter.sh never sends from a shared pool. Each newsletter sends through an email provider account that you own, from a domain you control, so your reputation is yours alone and nobody else's mistakes can hurt it.
You choose the provider per newsletter with the picker in Settings → Sending. Amazon SES is the default and the one we recommend for most newsletters. If you already send through another provider, you can keep it.
Supported providers
Eleven ways to send. The connection details differ; everything after that works the same.
| Provider | How you connect | Regions | Feedback |
|---|---|---|---|
| Amazon SESDefault | IAM access key and secret, and a region | Any SES region | SNS events, signed |
| Postmark | Server API token; an account token is optional | — | Webhook, authenticated |
| SendGrid | API key with Full Access | Global or EU | Event webhook, signed (ECDSA) |
| Mailgun | Private API key and region; sending subdomain and webhook signing key optional | US or EU | Webhooks; signed once you add the signing key |
| Resend | API key with full access, and a domain region | US, EU, São Paulo or Tokyo | Webhook, signed (Svix) |
| Brevo | API key | EU-based | Webhook, authenticated |
| Mailjet | API key and secret key | EU-based | Event webhooks, authenticated |
| SparkPost | API key and region | US or EU | Webhook, authenticated |
| Elastic Email | API key with full access | — | Webhook, signed (Pro plan) |
| SMTP2GO | API key | — | Webhook, authenticated |
| Your own SMTP | Host, port (STARTTLS on 587 or TLS on 465), username and password | Your server | Send-time rejections, plus a signed events URL |
Every webhook is registered for you and arrives at a private URL for your newsletter. “Signed” means the provider signs each request and the signature is verified; “authenticated” means the request must carry a secret only the platform and the provider know. “Your own SMTP” covers any server or relay you run, such as Postal, Haraka or Postfix.
Which one should I choose?
- Amazon SES is the cheapest at scale and the default. Pick it unless you have a reason not to. New AWS accounts start in a sandbox, so allow a day for production access.
- Postmark is known for excellent inbox placement. Newsletters go through a Broadcasts message stream, kept apart from your transactional mail.
- Mailgun or SparkPost if you want an EU region; Brevo and Mailjet are EU-based.
- Any provider you already use, if your domain is set up there. Reusing it is the quickest start.
- Your own SMTP server if you run your own mail infrastructure. You get full control, and you also own IP reputation, blocklist monitoring and bounce reporting.
Connecting a provider
In Settings → Sending, pick a provider and work through its four steps. Only owners can change sending settings, and your current provider keeps sending until you switch.
- Connect your accountPaste the key (or SMTP login) and pick a region where it applies. The credentials are checked live, then encrypted. They are never shown again, only their last four characters.
- Verify your domainWhere the provider's API allows it, the platform adds your sending domain there for you. It shows the exact DNS records the provider needs and checks them itself on public DNS rather than taking the provider's word for it: every minute for 20 minutes after you publish them, then daily. See Domain authentication.
- Bounce and complaint feedbackThe platform registers the provider's webhook automatically, signed or authenticated, so bounces, complaints and deliveries flow back to your newsletter.
- Send a test emailA real email goes to you through the whole pipeline. When all four steps are done, click Use {provider} to start sending with it.
Amazon SES has its own checklist (an account probe, quota and a configuration set), covered in Amazon SES.
What the platform handles
These work identically whichever provider is active:
- Tracking and analytics. Opens and clicks are tracked by newsletter.sh itself, with the provider's own tracking switched off, so reports are comparable across providers.
- One-click unsubscribe.
List-UnsubscribeandList-Unsubscribe-Postheaders on every email. - Suppression. Hard bounces are suppressed straight away, soft bounces after three different campaigns, and complaints immediately, with an alert. See Bounces and complaints.
- Health score and spam score. The same checks and thresholds on every provider.
- Warm-up and engaged-first ordering. See Deliverability.
Speed and limits
Each provider has a sensible default send rate and batch size built in. Under Speed and limits an owner can change the requests per second, which is shared by every newsletter on the same provider account, and set an optional daily limit to match their plan. Sends over the limit continue the next day.
Provider details
Anything specific to a provider beyond the key and the DNS records:
- Newsletters must go through a Broadcasts message stream. The platform finds yours automatically; create one under Message Streams if you don't have it yet.
- The account token is optional. With it, the platform adds your domain at Postmark for you.
- Postmark reviews new accounts before they can send to everyone.
- Use an API key with Full Access, so the platform can set up the domain and the event webhook.
- Event webhooks are signed (ECDSA) and verified.
- Choose the US or EU region to match your Mailgun account.
- Add the HTTP webhook signing key (optional) to turn on signature checks.
- If you send through a subdomain at Mailgun, such as mg.yourdomain.com, enter it as the sending domain.
- Large sends go out in batches of 100, each with an idempotency key so a retry never sends twice.
- Webhooks are signed with Svix and verified.
- Open and click tracking are turned off on the domain at Resend, because newsletter.sh does its own.
- Brevo adds its own unsubscribe header. Unsubscribes made through it are mirrored here automatically.
- Sends go out in batches of 50.
- Mailjet allows one webhook URL per event type, so the platform only uses the event types it needs and never overwrites yours.
- Unsubscribe events from Mailjet are mirrored here.
- Choose the US or EU region.
- SparkPost adds its own unsubscribe header. Unsubscribes made through it are mirrored here automatically.
- Elastic Email's policy requires double opt-in for newsletters.
- Its webhooks need the Pro plan. They are signed and verified.
- Turn off open and click tracking on the API key in SMTP2GO, so only one set of tracking runs.
- Unsubscribe events from SMTP2GO are mirrored here.
Your own SMTP server
- Connections are encrypted: STARTTLS on port 587 or TLS on port 465.
- Mailbox hosts are blocked: Gmail, Outlook and Office 365, Zoho, iCloud, Yahoo, plus ZeptoMail and Mandrill.
- An address your server rejects during sending is suppressed immediately.
- For bounces and complaints that arrive later, have your server POST them as JSON to the events URL shown in Settings → Sending, step 3, signed with the events secret shown there.
POST {events URL from Settings → Sending, step 3}
Content-Type: application/json
X-Newsletter-Sh-Signature: t=1763458867,v1=6c1f…
{
"events": [
{
"type": "bounce",
"email": "ada@example.com",
"messageId": "<20261118094107.abc123@mail.yourdomain.com>",
"bounceType": "hard",
"reason": "550 5.1.1 User unknown",
"timestamp": "2026-11-18T09:41:07Z"
}
]
}| Field | Value |
|---|---|
type | bounce, complaint, delivered, deferred or rejected |
email | The recipient's address |
messageId | The Message-ID of the email it refers to |
bounceType | hard or soft, for bounces |
reason | The diagnostic, such as the SMTP reply |
timestamp | When it happened |
The X-Newsletter-Sh-Signature header is t=<unix seconds>,v1=<hex HMAC-SHA256>, computed over {t}.{body} with your events secret:
import crypto from "node:crypto";
// Sign the exact body you send, with the events secret from Settings → Sending, step 3.
const body = JSON.stringify({ events });
const t = Math.floor(Date.now() / 1000);
const v1 = crypto.createHmac("sha256", secret).update(`${t}.${body}`).digest("hex");
await fetch(eventsUrl, {
method: "POST",
headers: { "Content-Type": "application/json", "X-Newsletter-Sh-Signature": `t=${t},v1=${v1}` },
body,
});Switching providers
Once a provider has finished its four steps, click Use {provider}. You can switch back to Amazon SES the same way.
- Switching is refused while a campaign is sending. Wait for it to finish, or pause it first. A paused campaign resumes on whichever provider is active when you resume it.
- Mail already sent keeps reporting bounces and complaints through the provider that sent it, so nothing is lost when you switch.
- Warm-up restarts from day one if warm-up is on, because the new provider's IPs have no history with your domain. You can opt out. If warm-up is off and your list is more than a few thousand readers, turn it on before switching.
- Your subscribers, suppression list, reports and archive stay exactly as they are.
Not supported
Some popular services are left out on purpose. Most are mailbox or transactional services whose terms don't allow bulk newsletter mail, and sending through them risks your account being closed mid-campaign. Their SMTP hosts are also refused by the SMTP option.
| Service | Why |
|---|---|
| Zoho ZeptoMail and Zoho Mail SMTP | Transactional or personal mail only; newsletters and marketing mail are not allowed. |
| Gmail, Google Workspace, Outlook / Microsoft 365, iCloud and Yahoo SMTP | Personal mailboxes: bulk mail breaks their terms, and their small daily caps would stall sends. |
| Mailchimp Transactional (Mandrill) | Transactional mail only; bulk marketing has to go through Mailchimp itself. |
| MailerSend | Not supported yet. |