All email now delivered from the EU
Every message we send, yours to your contacts and ours to you, is delivered by Amazon SES in Frankfurt.
One suppression list, two streams
A single suppression list covers customer sending and our own account mail, and it is enforced at send time rather than at list-build time. A bounce or a complaint blocks every stream, because both are statements about whether the address can receive mail at all. An unsubscribe blocks marketing only, because it is a statement about consent rather than about deliverability.
Deliveries, bounces and complaints come back through a signed event pipeline and are processed within seconds, so the list reflects reality rather than yesterday's reality.
Why the region is on the changelog
For a product sold to European teams, where mail is processed is a contractual question rather than an implementation detail. Moving account mail onto the same provider and region as customer sending means there is one answer to it instead of two, and the sub-processor list has one fewer name on it.
It also removes a class of answer nobody enjoys giving, which is the one where the customer-facing pipeline is in the right region and the password reset is not.
Also in this release
- The groundwork shipped first: the sending layer ran on Amazon SES alongside the previous provider for a period, including bounce and complaint handling through a dedicated SES webhook.
Related: EU data residency, GDPR and sub-processors
Private beta
See the next one land
Beta members get the release note in the same batch email that opens their account.