
Email API
452 4.5.3 too many recipients: limits by provider and how to fix it
452 4.5.3 means the server took some recipients and refused the rest because one message or session named too many. Split the send into smaller batches.
6 min read

452 4.5.3 means the server took some recipients and refused the rest because one message or session named too many. Split the send into smaller batches.
6 min read

Pick an email agent's daily send cap from your own data: run in Suggest first, count replies you approve unchanged, then set the cap just above a normal day.
5 min read

Two email agents can reply to each other forever. Stop it with Auto-Submitted checks, one reply per thread, a daily cap and a duplicate hold. A practical list.
6 min read

Respect Retry-After, smooth bursts with a token bucket and keep retries idempotent. A practical guide to living within an email API's rate limits.
4 min read