Definition
Email throttling is the practice of controlling the rate at which emails are sent to prevent overwhelming receiving mail servers or triggering spam filters. Internet service providers (ISPs) such as Gmail, Outlook.com, and Yahoo enforce per-connection rate limits. Sending too many messages too quickly from a single IP address triggers these limits, resulting in deferred deliveries, temporary blocks, or permanent listing on deny lists.
Throttling is typically implemented at the ESP level by distributing sends over a configurable window. Rather than sending 100,000 emails instantly, a campaign is spread across 2 to 8 hours at thousands of messages per minute. The rate depends on the sender's reputation, the IP's warm-up status, and the ISP's specific limits. A new dedicated IP may be limited to 50 to 200 messages per connection per hour, while a fully warmed IP can handle tens of thousands per hour.
Best Practices
Start every new sending IP with a gradual warm-up schedule. Send small volumes (100 to 200 emails per day) for the first week, doubling volume weekly over 4 to 8 weeks until reaching full sending capacity. ISPs track sending patterns; a sudden spike from a new IP is a strong spam signal. Warm up shared IPs alongside the ESP's aggregate reputation, but monitor your own sending patterns independently.
Configure your ESP to respect per-ISP rate limits. Most platforms (SendGrid, AWS SES, Mailgun, Postmark) allow you to set a maximum send rate per minute or per hour. Set these limits conservatively — under 50 messages per second for warm IPs, and much lower for cold IPs. Monitor ISP-specific bounce rates and adjust the throttle downward if you see increased deferrals or 4xx SMTP responses.
Distribute sends across multiple IP addresses and subnets to bypass per-connection limits. Large senders use IP pools with 10 to 50 IP addresses, rotating through them for each SMTP connection. Automate the IP rotation at the application or ESP level. Never send all traffic through a single IP if your volume exceeds 50,000 emails per day.
Send during the recipient's local business hours to improve engagement and reduce throttling. ISPs factor in engagement signals (opens, clicks) when deciding whether to throttle. Emails sent during off-hours generate fewer opens, which signals disinterest and leads ISPs to tighten rate limits. Use time-zone-based sending to deliver emails when the recipient is most likely to engage.
Related Glossary Terms
Bounce Classification
Bounce classification uses SMTP codes (550, 551, 552, 553, 554, 450, 451, 452) and enhanced status codes to categorise permanent and transient delivery failures.
DMARC Alignment
DMARC identifier alignment determines whether the domain in the From header matches the domains used in SPF and DKIM authentication. Strict or relaxed.
Email Active Subscriber
An active email subscriber has opened or clicked an email within a defined recency period, typically 30-90 days by industry. Active subscriber rate of 40-60% is typical for healthy email lists.
Email Blacklist
An email blacklist (DNSBL) is a real-time database of IP addresses or domains known for sending spam or unwanted email.
Email Bounce
The return of an undelivered email to the sender, categorized as hard, soft, or transient with distinct handling rules for each.
Email Bulk
Bulk email classification distinguishes mass commercial messages from transactional emails, with specific authentication requirements for senders over 5,000 daily.
Frequently Asked Questions
Throttling is a temporary rate limit — emails are deferred and retried later. Blocking is a permanent rejection — emails are returned as hard bounces or silently dropped. A throttled email may be delivered minutes or hours later; a blocked email is never delivered. Throttling is recoverable; blocking often requires manual delisting.
Gmail limits the number of messages accepted per SMTP connection and per hour per sending IP. Typical limits are around 2,000 messages per connection and 20,000 to 50,000 per 24-hour window for a warmed IP. Exceeding these limits returns a 4xx (try again) SMTP response. Gmail dynamically adjusts limits based on sender reputation.
Most ISPs require 4 to 8 weeks of gradual volume increase to build full sending reputation. Start at 100 to 200 emails per day and double weekly. A sudden jump to 10,000 emails per day from a brand-new IP will almost certainly trigger throttling or blocking.
Yes. If you consistently hit ISP rate limits and accumulate deferrals, ISPs interpret the retry traffic as low-quality sending. High deferral rates hurt your reputation. Throttling should be planned and gradual, not a reaction to hitting limits — reactive throttling indicates poor capacity planning.
For a fully warmed IP with good reputation, 50,000 to 100,000 emails per day is typical. The safe per-second rate depends on the target ISP. A rate of 10 to 50 messages per second is generally safe for major ISPs. Always monitor bounce rates and deferrals and reduce the rate at the first sign of trouble.