Skip to content

0024. Amazon SES with one tenant per workspace, and our own sender protection

  • Status: Accepted
  • Date: 2026-11-08

The managed service sends all customers’ mail from shared provider infrastructure, so one workspace’s bad list can damage everyone’s reputation or get the provider account paused. Facts checked 2026-11-07 and 2026-11-08:

  • SES costs $0.10 per 1,000 emails on à la carte pricing. New accounts default to the Essentials pricing plan ($0.16 per 1,000) but can switch to à la carte immediately, per region.
  • SES supports tenants, each with its own reputation and status; SES can pause a tenant and publishes tenant status changes to EventBridge.
  • The SES management API is limited to 1 request per second per account, and the limit cannot be raised.
  • SES has no idempotency key and no status lookup (ADR 0012).

Provider setup:

  • Amazon SES is the email provider of the managed service from day one. The new account is switched to à la carte pricing.
  • One workspace is one SES tenant. SES suppression is tenant-level, not account-wide.
  • Our suppression is workspace-scoped, matching the SES tenant: an address suppressed by a hard bounce or complaint in one project is suppressed in every project of the workspace, and never in another workspace. The workspace’s suppression list is kept in D1 (the Postgres control schema in containers), keyed by a per-workspace HMAC of the address, and replicated to each project store of the workspace through a queue, so claimSend checks it inside its transaction. Until a new entry arrives, SES’s tenant-level suppression drops the send.
  • A send that SES drops because the address is on its suppression list is not billable (ADR 0012).
  • Configuration sets are global, one per stream: transactional and marketing. Per-workspace configuration sets are created only for dedicated IPs.
  • Each workspace stores a provider_account_id, so workspaces can later be spread across several SES accounts.
  • We check sending-domain DNS records (DKIM, SPF, DMARC, MAIL FROM) ourselves and call the SES management API only when something changes.
  • Sends are paced by the DeliveryRateLimiter per provider account.

Sender protection:

  • We pause a workspace’s stream before SES pauses its tenant: warn at 2% bounce rate or 0.05% complaint rate; pause at 4% bounce rate or 0.08% complaint rate. Rates are computed per stream and only above a minimum sample size.
  • We consume SES tenant status events from EventBridge and reflect a tenant pause in the workspace immediately.
  • Global and per-workspace send kill switches are checked in claimSend (ADR 0011).

Unsubscribe:

  • Marketing mail carries RFC 8058 one-click unsubscribe: List-Unsubscribe with an HTTPS URL containing a token, and List-Unsubscribe-Post: List-Unsubscribe=One-Click.
  • Only a POST with a valid token unsubscribes. A GET shows a page and never unsubscribes, because link scanners follow GET links.
  • We verify that the DKIM signature covers the List-Unsubscribe and List-Unsubscribe-Post headers.

Self-hosting does not require SES or an AWS account beyond what the self-hoster chooses (ADR 0003); the adapter interface stays provider-neutral.

  • Delivery events, metering, and unknown-outcome handling follow ADR 0012.
  • Our own system mail (sign-in codes, account mail, notifications) does not use this SES account; see ADR 0029.
  • Open: the minimum sample size for auto-pause, and the transport for SES events (SNS with signature verification and subscription confirmation, or an EventBridge API destination with authentication).