Fake emails rely on urgency, impersonation, and visual tricks. Learning the signs lets you slow down and evaluate before acting. Sender domain mismatches,...
Key takeaways
- Mailbox hosts (Gmail, Google Workspace, Microsoft 365, shared hosting) enforce daily and/or hourly sending caps that are separate from any outreach tool’s settings.
- Limits change. Treat published numbers as guidance and verify against your provider’s primary docs and your own plan before a high-volume send.
- Google Workspace paid accounts: up to 2,000 messages per rolling 24 hours (500 on trial). Microsoft 365 / Exchange Online: typically 10,000 recipients per mailbox per day, plus 30 messages per minute — and a tenant-level external recipient cap (TERRL).
- Hitting a hard limit usually means a temporary send block (often hours to a day). Spikes, poor list quality, and high bounces can also trigger abuse controls even when you are under the numeric cap.
- Before you scale volume, validate addresses so invalid and risky contacts do not burn quota and reputation at the same time.
Email hosts cap how much you can send — per minute, per hour, or per rolling day. Those caps protect the shared infrastructure and reduce abuse. If you run campaigns, transactional scripts, or CRM automations through a personal or business mailbox (SMTP, IMAP, or webmail), the host’s limit — not your sending tool alone — decides when you get deferred, rejected, or temporarily blocked.
This guide summarizes common limits for free Gmail, Google Workspace, Microsoft 365, GoDaddy Professional Email, Rackspace, Bluehost, DreamHost, HostGator, and Yahoo Mail. Figures for Google and Microsoft are grounded in primary documentation as of August 2026. Shared-hosting and consumer Yahoo figures can vary by plan and are less consistently published — always confirm in your control panel or with support before a large send.
Why mailbox sending limits matter
You must know your provider’s limits when you send through tools that use your own SMTP. The tool may gladly queue thousands of messages; the mailbox will not. Crossing the cap often means you cannot send new mail for roughly 1–24 hours (and sometimes longer if the account is flagged for spam-like behavior).
Limits also stack with follow-ups and concurrent campaigns. First-touch messages plus automated replies can fill the same daily recipient budget. Scheduling everything into a short “golden hour” window is a common way to trigger hourly or per-minute throttles even when the daily total looks fine.
Finally, hosts weigh quality as well as quantity. High bounce rates, spam complaints, and sudden volume spikes can restrict sending before you hit the published number. Keeping lists clean is part of staying under practical — not only theoretical — limits. See also our guide on how to avoid spam filters and how to check domain reputation.
Mailbox email vs. a dedicated ESP
Workspace and hosting mailboxes are built for person-to-person and light operational mail. They are a poor fit for newsletters, cold sequences at scale, or large transactional bursts. Dedicated email service providers (ESPs) and products such as Microsoft’s Azure Communication Services Email exist for higher volume, with their own reputation and compliance models.
If you regularly need more than a few hundred external messages per day from one mailbox — or you keep hitting TERRL / daily caps — move marketing or bulk traffic to a purpose-built sender and keep the primary mailbox for human and low-volume system mail.
How limits are counted (messages vs. recipients)
Providers do not all count the same way:
- Messages — each send counts as one (Google Workspace’s primary daily message cap works this way).
- Recipients — one message to 10 people can count as 10 toward the day (Microsoft 365 and Rackspace emphasize recipient counts).
- Unique recipients — Google Workspace also tracks unique addresses and external unique recipients separately.
- Per-minute / per-hour rates — Exchange Online’s 30 messages per minute and many shared hosts’ hourly caps stop burst sending.
When you model capacity, multiply your average recipients-per-message by expected sends, then leave headroom for replies, calendar invites, and other day-to-day mail from the same address.
Provider limits
Numbers below are typical published ceilings for accounts in good standing. Providers can change them without notice, apply lower abuse-based rates, and enforce different rules for trial, SMTP, API, and mail-merge paths.
Free Gmail
Practical daily ceiling: about 500 messages / recipients per day (rolling). Exceeding it usually blocks sending for 1–24 hours.
Google’s consumer help for Gmail states that you may hit a sending limit if you address more than about 500 recipients in a single message and/or send more than about 500 emails in a day. There is no useful official “hourly” table for free Gmail; treating the account like a bulk ESP is still a bad idea. Prefer a business domain on Google Workspace for serious outbound volume, and keep free Gmail for personal or very light use.
Content quality still matters: invalid recipients and bounce-heavy lists can restrict sending even when you stay under 500. Google’s own help notes delivery failures and bounce patterns as reasons messages may stop going out.
Google Workspace (formerly G Suite)
Paid accounts: up to 2,000 messages per user per rolling 24 hours (1,500 for mail merge / multi-send). Trial accounts: 500 messages per day.
Per Google Workspace Help — Gmail sending limits, additional caps that commonly affect outreach include:
- Recipients per message (web Gmail): up to 2,000 total, maximum 500 external
- SMTP via POP/IMAP clients: 100 recipients per message
- Gmail API: 500 recipients per message
- Total recipients per day: up to 10,000 (1,500 for mail merge)
- Unique recipients per day: up to 3,000 (2,000 external; 500 external on trial)
Google states that sending limits can change without notice and that limits are applied over a rolling 24-hour period. Exceeding a limit typically prevents new sends for up to 24 hours while mail still arrives.
Trial → paid does not instantly unlock the full quotas in every case. Google documents that after converting to paid, higher Gmail sending limits apply once the domain has cumulatively paid at least $100 USD (or equivalent), and that it can take substantial time after that threshold for the increase to fully apply. Always verify current behavior in the admin help articles linked above — not in third-party blog tables alone.
SMTP relay through Google has separate, higher organizational limits and is documented separately from user Gmail quotas.
Microsoft 365 (Exchange Online)
Per mailbox: 10,000 recipients per day (24-hour sliding window) and 30 messages per minute. Default recipients per message: 500 (customizable up to 1,000).
These figures come from Microsoft’s Exchange Online limits and Defender for Office 365 guidance on outbound sending. After the recipient rate limit is reached, the mailbox cannot send until the past-24-hour recipient count drops below the cap.
Microsoft also enforces a Tenant External Recipient Rate Limit (TERRL): a tenant-wide daily ceiling on external recipients that scales with the number of email licenses (trial tenants are capped lower — Microsoft documents 5,000 external recipients per day for trial). Admins can review usage in Exchange admin center reports (Tenant Outbound External Recipients). Hitting TERRL can block external sending for the whole tenant even if individual mailboxes are under 10,000.
Exchange Online is not designed for bulk marketing. Microsoft recommends Azure Communication Services Email or another bulk provider when you need sustained high external volume. Default onmicrosoft.com sending domains have additional, much tighter external caps — use a custom accepted domain for production mail.
GoDaddy Professional Email (powered by Titan)
Per GoDaddy Help: 1,500 messages per day via webmail; 500 messages per day via SMTP; 100 recipients per message.
Source: Professional Email account limitations. If your shop still uses a legacy Workspace Email product or Microsoft 365 sold through GoDaddy, limits differ — Microsoft 365 follows Exchange Online rules above; legacy Workspace figures published on older third-party pages (for example ~250–500 recipients/day) may not apply to Titan Professional Email. Check which product you actually have in the GoDaddy account before planning campaigns.
Automation that speaks SMTP will typically hit the lower 500/day path first. Spread follow-ups across days and mailboxes if you must stay on this stack.
Rackspace Email
10,000 recipients per email address per calendar day (Eastern time window), counting recipients — not merely messages.
Confirmed in Rackspace documentation and postmaster materials: one message to 100 people counts as 100 recipients toward the day. Automated or spam-classified traffic may be held to much lower rates. Rackspace reserves the right to change limits to protect the service. High bounce or complaint rates can restrict you under the numeric ceiling.
Bluehost
Shared plans commonly advertise 500 outgoing emails per hour. Some Bluehost help articles still describe a default of about 150 per hour that support can raise.
Treat Bluehost as hourly-capped shared hosting, not a bulk ESP. Confirm the active hourly value on your plan comparison page or with support before a send. Exceeding the hourly maximum typically produces deferrals or bounce errors until the next window. Sustained marketing volume usually belongs on a dedicated email platform or higher-tier hosting with different mail policies.
DreamHost
SMTP (clients, webmail, authenticated forms): 100 recipients per hour per address, up to 100 recipients per message (shared). Script/shell sending on shared servers has its own per-server caps; VPS/dedicated PHP/CGI sending and discussion lists are documented differently.
DreamHost’s knowledge base article on SMTP quota limits stresses that quotas are based on recipients, not message count, and that shared SMTP limits are not freely adjustable. For announcement-style mail to many people, use the tools DreamHost documents for lists rather than blasting SMTP from a shared mailbox.
HostGator
Shared / reseller: 500 outgoing emails per hour per domain (addon and subdomain each get their own 500/hour). Lists over ~900 addresses: off-peak only. Lists over 5,000: VPS or dedicated required.
HostGator’s mail policy describes these shared-hosting restrictions clearly; VPS and dedicated accounts are not held to the same hourly shared caps. You cannot “split” a large list into smaller ones on shared hosting to dodge the 5,000 rule. Plan capacity as 500 × hours you actually send — not a theoretical 12,000/day if you cannot sustain peak-hour sends under policy.
Yahoo Mail / Yahoo Mail Plus
Yahoo does not publish a crisp official daily table comparable to Google Workspace Help. Industry reports commonly cite roughly 500 outgoing messages per day and about 100 recipients per message; hourly figures are unofficial.
Yahoo may pause sending when volume looks abusive and will show a wait time. There is no reliable paid “raise my Yahoo SMTP cap for cold email” path. For anything beyond light personal or small-business correspondence, use a business mailbox or ESP instead of Yahoo SMTP.
Quick comparison table
| Provider | Typical published ceiling | Confidence |
|---|---|---|
| Free Gmail | ~500 / day | Google consumer Help |
| Google Workspace | 2,000 messages / day (500 trial); extra recipient caps apply | Google Workspace Help |
| Microsoft 365 | 10,000 recipients / mailbox / day; 30 msg / min; plus TERRL | Microsoft Learn |
| GoDaddy Professional Email (Titan) | 1,500 / day webmail; 500 / day SMTP; 100 recipients / message | GoDaddy Help |
| Rackspace Email | 10,000 recipients / day | Rackspace docs |
| Bluehost (shared) | Often 500 / hour (confirm; some docs cite ~150 default) | Plan pages / Help — verify |
| DreamHost (SMTP shared) | 100 recipients / hour | DreamHost KB |
| HostGator (shared) | 500 / hour per domain; list-size rules | HostGator mail policy |
| Yahoo Mail | ~500 / day (commonly reported) | Not crisply published — verify |
Last reviewed August 2026. Re-check primary documentation before relying on any row for production capacity planning.
Stay under the cap without stalling the campaign
- Model recipient math — include To/Cc/Bcc and every automated follow-up on the same mailbox.
- Spread volume — longer send windows beat sharp one-hour spikes that trip per-minute and per-hour rules.
- Warm gradually — a quiet mailbox that suddenly sends hundreds of cold messages looks abusive even when the daily number is legal.
- Separate roles — keep marketing on an ESP; keep the human mailbox for replies and light CRM mail.
- Watch authentication — SPF, DKIM, and DMARC do not raise sending quotas, but they reduce “spam-like” outcomes that trigger soft blocks. See our SPF, DKIM, and DMARC overview.
Validate before high-volume sends
Sending limits and list quality interact. Every hard bounce still consumes a recipient slot on many platforms and teaches filters that your stream is risky. Before you push toward a Workspace, Microsoft 365, or shared-host ceiling, run the list through an email validation workflow so clearly invalid, disposable, and toxic addresses are removed or held back.
Validation does not guarantee inbox placement and does not raise your provider’s numeric cap. It does reduce wasted quota and the bounce-driven restrictions that often appear before you hit the official maximum. For mailbox existence checks without blasting a campaign, see how to verify an email address without sending an email. Catch-all domains need extra care — start with keep or delete accept-all emails.
Conclusion
Choose the host that matches how you actually send: light personal mail, business collaboration, or true bulk delivery. Free Gmail and Yahoo are poor bulk engines. Google Workspace and Microsoft 365 raise the ceiling for business mail but still throttle bursts and (for Microsoft) entire tenants via TERRL. Shared hosts add hourly and list-size rules that surprise teams who only memorized a “per day” rumor.
Whatever stack you use, verify today’s numbers in the provider’s own docs, leave headroom for ordinary mail, and clean the list before you scale. That combination protects both your sending privileges and your domain’s long-term deliverability.
