Email sending limits depend on the account, service, sending method, and time window. They can count messages, recipients, external recipients, or an entire organization’s traffic. Check the unit before comparing providers.

This guide links to current provider documentation for 2026. A published limit is a service ceiling; it does not establish that a cold outreach campaign is permitted or that recipients will see the mail in their inboxes.

What are email sending limits?

A single email to ten recipients may count as one message and ten recipients. Mailbox limits can also apply alongside tenant-level limits and anti-abuse controls. A provider can throttle or block sending below a published ceiling when it detects unwanted traffic.

Count new outreach, follow-ups, normal business correspondence, and automated messages when planning capacity. Keep recipient-side sender requirements separate from the limits imposed by the service you send through.

Gmail and Google Workspace

Use Google’s Workspace sending limits for managed business accounts. Account status and sending method affect the allowance; trial, mail merge, and SMTP workflows may have different limits. A personal Gmail account has a different set of restrictions.

Check the rolling measurement window and the separate message and recipient rules that apply to your setup. Do not rely on old advice that paying a fixed amount immediately unlocks a particular limit.

Google’s sender guidelines for personal Gmail recipients are another set of rules. They cover authentication and unwanted mail, with additional requirements for bulk senders. Satisfying them does not increase your sending account’s allowance.

Microsoft 365 and Outlook.com

Exchange Online business accounts and personal Outlook.com accounts are different services. Use Exchange Online limits for business sending and Outlook.com’s sending-limit guidance for the consumer service.

Exchange Online has mailbox recipient limits, message-rate limits, and tenant external recipient restrictions. Do not describe a recipient allowance as an allowance for that many separate emails, or assume the same quota applies to a newly created personal account.

Microsoft canceled the proposed Mailbox External Recipient Rate Limit in January 2026. This did not cancel other recipient, tenant, or anti-abuse restrictions. Read the current documentation rather than using an older rollout announcement as the operative rule.

For mail delivered to Outlook.com consumers, also check Microsoft’s high-volume sender authentication requirements. Those receiving-side requirements have a different scope from your Exchange Online sending capacity.

Zoho Mail

Zoho’s current limits documentation describes a rolling hourly window and dynamic external sending limits. It also separates account type and internal or external recipients.

Read the Zoho Mail usage policy before selecting it for a campaign. Zoho Mail is intended for ordinary business and personal correspondence; the policy excludes bulk, marketing, and automated email use. A technical quota does not override those restrictions.

Yahoo and other providers

Yahoo’s sending-limit guidance explains that accounts may be temporarily restricted when limits are reached. Do not substitute a third-party daily estimate for the allowance actually applied to your account.

For every provider, check the account dashboard, current help pages, administrator settings, and acceptable-use rules. Limits for a transactional service or newsletter platform are not interchangeable with mailbox SMTP limits.

How much outreach should you send?

There is no universal number that guarantees inbox placement. Start with a small, relevant, verified audience and observe provider responses, complaints, and qualified replies. Increase gradually only when you understand the results.

Plan for every step of a sequence. If tomorrow’s follow-ups already consume your intended capacity, reduce new enrollments rather than letting the queue exceed your mailbox’s operating limits.

Limits are only one part of delivery

Check SPF, DKIM, and DMARC alignment, invalid addresses, repeated unwanted messages, and provider rejection codes. A successful send or SMTP acceptance does not prove inbox placement.

A verification result is also not consent or proof of interest. Keep a shared suppression list and stop contacting people who object. Separate authentication problems from list quality and relevance so you can fix the actual cause of a rejection.

Scale a process you can monitor

In your sending platform, set mailbox caps and sending windows, count follow-ups, and pause affected campaigns when errors increase. Confirm replies and opt-outs stop the right sequences across the team.

QuickMail can help organize campaigns and mailbox activity, but software does not override the provider’s limits or policies. Review both the platform allowance and the connected mailbox or tenant restrictions before adding traffic.