Email Rate Limit

Definition

Email rate limits are the restrictions that mailbox providers place on how many messages they will accept from a sender within a given time period. These limits operate at multiple levels: per-connection (messages per SMTP connection), per-second (messages per second from an IP), per-hour, and per-day. Limits are dynamic and unannounced, adjusted by each mailbox provider based on the sender's reputation and sending history. Understanding and managing rate limits is essential for maintaining high inbox placement and avoiding blocks.

Each major mailbox provider has a different approach to rate limiting. Gmail uses a reputation-based system where new senders typically start at 100-200 emails per second per IP, with the limit increasing as the sender demonstrates good behaviour. Outlook/Hotmail is notably more conservative, starting new senders at 30-50 emails per second and increasing slowly based on complaint and bounce rates. Yahoo and AOL are generally more permissive, with initial limits of 200-500 per second. All providers have hard daily volume caps that vary by sender reputation. For senders with poor reputation or a history of abuse, limits may be reduced to 10-20 per second.

Rate limit detection and self-regulation is a key MTA function. When a sender exceeds a mailbox provider's rate limit, the provider responds with a temporary failure code (4xx, typically "too many connections" or "try again later"). A well-configured MTA detects these responses and automatically reduces sending to the affected provider, then gradually increases as the provider's responses return to normal. Self-regulation prevents the escalations that occur when senders ignore deferral responses: continued over-sending can result in IP blocking, temporary blacklisting, or permanent reputation damage.

Best Practices

Implement per-ISP throttle controls in your MTA configuration. Rather than using a single global send rate, configure separate throttle settings for each major ISP based on their known limits. Monitor deferral rates per ISP and adjust throttles dynamically. Many commercial MTAs support automatic throttle adjustment based on real-time deferral feedback.

Start new IPs at conservative rate limits and increase gradually during warmup. A new IP should start sending at 25-50 emails per second maximum, regardless of ISP capacity. Increase the rate by approximately 10-20% per week during warmup, monitoring deferral and complaint rates at each increase level. Full rate capacity is typically achieved after 6-12 weeks of consistent positive sending behaviour.

Monitor the percentage of 4xx responses per ISP as a rate limit indicator. The acceptable threshold varies by ISP, but as a general rule, if more than 5-10% of your deliveries to a specific ISP are receiving 4xx deferrals, you are approaching or exceeding their rate limit. Reduce sending to that ISP until the deferral rate drops below 3%.

Distinguish between rate limit deferrals and other 4xx deferrals. Not all 4xx codes indicate rate limiting. Mailbox providers use different codes for rate limiting (e.g., 420, 450 4.2.0, or custom messages) vs transient delivery issues (server busy, temporarily unavailable). Configure your MTA to detect rate-limit-specific codes and apply throttle reduction only when those codes are received.

Plan campaigns to stay within your known rate limits rather than hitting limits and backing off. A campaign that repeatedly hits rate limits creates a poor impression with mailbox providers and may lead to reputation downgrades. If your known rate limit is 200 MPS total, plan your campaign so that peak sending rate stays at 160-180 MPS, providing headroom for unexpected volume variations.