Abuse prevention and rate limits
Every limit here exists because a shared sending platform is only as deliverable as its worst sender. They are not a judgement about your traffic.
The limits you will actually meet
| Limit | What happens |
|---|---|
| Per-minute rate cap | 429 with Retry-After: 60 |
| Monthly allowance | 429 with Retry-After to the next UTC midnight |
| Recipients per send | hard cap of 100 across To, Cc and Bcc; a warning over 25 |
| Message size | 10 MB per attachment, 20 MB total, 30 MB body |
| Domain warm-up | a daily cap on a newly verified domain, which rises |
Your current cap is on GET /v1/tenant, and your sending health, including
whether the cap has been lowered, is on
GET /v1/reputation.
See Rate limits for the full behaviour and Timeouts and server errors for what is safe to retry.
Reputation can lower your cap
The platform measures bounce and complaint rates per workspace. A bounce rate
past the threshold moves a workspace to throttled and reduces its rate cap
until the rate recovers.
That is the one limit that is about your traffic, and it is also the one you can do most about:
- Do not send to addresses you have not verified exist. A list bought or scraped produces hard bounces immediately, and hard bounces are the fastest way to a throttle.
- Honour your own suppression list rather than removing entries to retry.
- Warm up rather than sending a campaign’s worth of mail on day one.
GET /v1/reputation reports the measured rate, the threshold it acts on, and
the current cap, so a throttle is diagnosable rather than mysterious.
Content scanning
Outbound mail passes Data Loss Prevention where a workspace enables it, and a
message matching a rule is refused with 422 Blocked by Data Loss Prevention
rather than sent. It runs before the test-mode divert, so test sends are
scanned too.
Inbound mail is scanned for malware and malicious links before it reaches a mailbox.
We do not publish the detail of what is detected or how. That is not evasiveness for its own sake: a published detection boundary is a map for whoever wants to cross it, and the people it would help most are not integrators.
If your traffic is legitimate and you are hitting limits
Caps are per workspace and are not fixed forever. Ask, with your expected volume and shape of traffic, rather than working around a limit by spreading sends across keys: keys share a workspace, so the cap is the same, and the pattern looks like evasion from the outside.