Source code
Security & compliance
Cost
Stability
No throttling
Part of the Email safety check · fix arrives as a guide
What it is
A send path has no rate limiting — a user or a loop can trigger unbounded messages.
Why it matters
It is a cost and a reputation problem at once. A retry loop or an abusive signup flow can send thousands of messages, and providers respond to the resulting complaint rate by throttling or suspending your account.
How to fix it
Rate-limit per recipient and per account on the sending path, and cap the total send rate for the process. Add idempotency to transactional sends so a retried request does not deliver twice.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.