Changelog

A domain another account has already verified is refused when you add it, with an explanation, rather than failing silently later.

Write a broadcast, pick an audience, and send — with a test send that puts the real message in your own inbox first.

Match the columns in your file to contact properties before the import runs, instead of renaming headers to suit us.

Select multiple contacts in an audience and remove them in a single action.

A rejected domain now explains the actual reason instead of returning a flat "Invalid domain name".

Adding a sending domain kicks off the DNS check immediately — no separate "verify" step to remember.

The email detail page shows the full history of a message, and explains failures and suppressions in plain language.

A message sitting in a deferred or queued state now says what that means and what happens next.

If your domain is at a supported DNS provider, we write the DKIM, SPF and Return-Path records for you.

Analytics break down how quickly Gmail, Outlook and the rest accept your mail, so a slow provider is visible.

Docs, status and a contact form that reaches a human, in one place.

eusend is listed in the MCP Registry, so clients can discover it by name.

One-click unsubscribe lands on a branded page we host, so a broadcast never needs an unsubscribe route of your own.

A skill that teaches Claude how eusend actually behaves — the API, the error codes, the domain setup.

The receiving server's own response is returned on the email, and sends stopped by a suppression are recorded rather than dropped.

Set open- and click-tracking defaults for the organization, and override them per broadcast.

The waitlist is gone. Create an account and send your first email in minutes.

Tag a send, filter by tag in the dashboard, and get the tags back on the webhook payload.

View the signing secret and cycle it from the dashboard — both secrets verify during the overlap, so nothing drops.

The email detail page translates the provider’s SMTP response into what actually went wrong and what to do about it.

One morning summary of the previous day’s sending, per organization.

A suppression list you can search, filter, export and clear — in the dashboard, the API and the SDKs.

Issue a key that can only send, or one restricted to a single sending domain.

Per-notification control over what eusend sends you.

OAuth sign-in alongside email and password.

Out-of-band bounces that arrive hours after the send now land on the message and feed reputation, instead of vanishing.

The Return-Path record is surfaced with your other DNS records, and alignment turns itself on once it resolves.

A data processing agreement you can sign, and a published list of every sub-processor we use.

Send mail, manage domains and read your logs from Claude, Cursor or Codex, without leaving the editor.

Typed clients for both, documented alongside the Node.js SDK.

The documentation moved to Fumadocs — full-text search, and copyable snippets in every language.

Disposable-address and blocklist checks at signup, so the shared sending reputation is not spent on throwaway accounts.

Billing, invoices and EU VAT are handled by Polar.

Per-key rate limiting, with the limits written down in the reference.

Every new account gets a sandbox sending domain and a runnable snippet, so the first send works before any records exist.

Engineering notes and product updates, at /blog.

Every scheduled job reports a check-in, so a cron that stops running pages us instead of going quiet.

Attachments are stored on our own S3-compatible storage in the EU.

Pass `scheduledAt: "in 2 hours"` or "tomorrow at 09:00" and we parse it.

Send up to a hundred messages in one call from any SDK.

The last managed queue dependency moved to self-hosted Valkey. Queues, database and MTA all sit in the EU on machines we control.

Attach files to any send, from the API or the SDKs.

Set a send time on an email or a broadcast and we hold it until then.

/llms.txt and /llms-full.txt, so a coding assistant can read the entire product in one fetch.

Warming up a new domain, and step-by-step migrations from SendGrid, Postmark, Mailgun and SES.

A staged ramp for a new sending domain, so volume grows at a rate inboxes accept.

Write a broadcast in a rich-text editor and send it to an audience.

Abuse reports from mailbox providers are ingested automatically and land on the message and the suppression list.

Mail to and from eusend requires TLS, published as an enforced MTA-STS policy.

Queue depth and deferral rates are watched continuously, and alert us before a provider’s throttling becomes your problem.

eusend moved off Amazon SES onto KumoMTA running on our own European hardware. Every message now leaves from IPs we control and warm ourselves.

Turn on TOTP two-factor authentication from account settings.

Point WordPress, Django, Rails or anything else at our SMTP host instead of rewriting it against the API.

Accounts created from disposable email domains are blocked at signup.

A typed client covering emails, domains, audiences, broadcasts and API keys.

Save a message once and reuse it across sends.

Retry a send safely — the same Idempotency-Key never delivers the same message twice.

Several workspaces per account, with keys, domains and logs scoped to each.

Keep contacts in lists, with unsubscribe state tracked per contact.

Invite teammates, assign roles, remove members and transfer ownership.

The first release: send a message with one POST, read back everything you sent, and send in batches.

Delivery, bounce and complaint events pushed to your endpoint as they happen.