How Many Emails Can You Send a Day? Limits by Provider (2026)

In February 2024, Google and Yahoo started rejecting bulk senders who didn’t meet new authentication rules. Microsoft joined them in May 2025, and non-compliant mail now gets bounced at the SMTP level instead of quietly landing in spam. So if you’re still sending the way you did in 2023, you’re one spam complaint away from a blocked domain. I’ve watched teams torch a two-year-old domain in a single afternoon because they treated “the provider lets me send 2,000” as “I should send 2,000.”

In this post, I’ll show you exactly how many emails you can send per provider in 2026, what the bulk sender rules changed, and how to protect your sender reputation while you scale volume.

What happens when you exceed a sending limit

Limits exist for a reason.

Before you launch a campaign, you need to know how many emails you can actually send without putting your sender reputation at risk.

Cross the limit your provider sets and you risk suspension. Sometimes that’s 24 hours. Sometimes it’s permanent. Neither one is a good morning.

There’s a second-order effect that hurts more. Send a large volume and watch a big chunk of it bounce because you blew past a cap, and your brand plus your sender reputation take the hit. Once that happens, your deliverability drops across every campaign you run, including the ones that were working fine.

The rules changed in 2024: what bulk sender status means for you

This is the part most “sending limits” articles still skip.

Provider caps tell you what’s technically possible. Bulk sender rules tell you what’s allowed. According to PowerDMARC’s breakdown of bulk email sender requirements, the guidelines kick in once you send 5,000 or more emails per day per domain, and they’re now enforced by Google, Yahoo, and Microsoft, with permanent rejections for non-compliance.

Cross that line and four things become mandatory:

• •

  SPF and DKIM, both set up and passing

• •

  DMARC, with a policy of at least p=none, aligned against SPF or DKIM

• •

  A one-click unsubscribe, implemented through the List-Unsubscribe headers defined in RFC 8058

• •

  A spam complaint rate below 0.3%

Now the concession: most B2B cold outreach never touches 5,000 a day to a single provider’s consumer inboxes. You probably won’t trip the bulk threshold.

Here’s why it matters anyway. The authentication baseline applies to everyone. SPF or DKIM is required of all senders, bulk or not, and the providers have shown they’re willing to reject rather than filter. Setting up SPF, DKIM, and DMARC before you scale costs you an afternoon. Not setting them up costs you a domain. If you’d rather not touch DNS records by hand, lemlist’s deliverability setup walks the authentication config for you.

Email sending limits by provider in 2026

There are two kinds of limits worth tracking. The hard caps imposed by your email service provider, and the softer volume you should actually send to keep campaigns healthy. Let’s start with the hard caps.

Providers set them to keep spammers out. Exceed them repeatedly and the provider can flag your account as spam and shut it down, which defeats the entire point of the exercise.

Here are 8 of the most popular providers and what they allow.

Pricing moves every year and varies by billing term and region, so check the provider’s own pricing page before you commit seats. The limits below are the numbers that actually constrain your campaigns.

Gmail and Google Workspace

Gmail is a cloud-based email service used by companies of every size, and it handles custom domain addresses, bulk sends, and everything in between. It’s built into Google Workspace.

Sending limits per day:

• •

  2,000 messages with a paid Google Workspace account

• •

  1,500 messages for mail merge (previously called multi-send), counted inside the 2,000

• •

  500 messages for trial accounts

Google Workspace Admin Help confirms these figures and notes something people miss: the daily limits are applied over a rolling 24-hour period, not a calendar day. Google also states the limits can change without notice.

Exceed one and you’ll see an error message like:

• •

  You have reached a limit for sending email.

• •

  You reached a Gmail sending limit.

• •

  You exceeded the maximum number of recipients.

Sending stops for up to 24 hours. You can still receive mail and use the rest of your account.

iCloud Mail

iCloud Mail is Apple’s email service, which integrates with your other Apple devices.

Sending limits:

• •

  1,000 messages per day

• •

  1,000 recipients per day

• •

  500 recipients per message

• •

  20MB message size, incoming and outgoing

Exceed them and you could see:

• •

  On your iPhone, iPad, or iPod touch: A copy has been placed in your Outbox. Sending the message failed because you exceeded your sending limit.

• •

  On your Mac: Cannot send messages using the server iCloud.

• •

  On iCloud webmail: Cannot send message. You have exceeded the total number of messages you can send each day (or you have exceeded the total number of recipients you can message each day). Or, Recipient limit exceeded. This message cannot be sent because it has too many recipients.

Microsoft Outlook

Outlook bundles email, calendar, contacts, and tasks in one place, with Office integration for sharing attachments from OneDrive and pulling up contacts.

The numbers depend entirely on which kind of account you’re on. Microsoft publishes the business figures in the Exchange Online limits documentation:

• •

  Microsoft 365 work and school accounts: 10,000 recipients per rolling 24 hours per user

• •

  500 recipients per message by default

• •

  30 messages per minute

• •

  Free Outlook.com accounts: roughly 300 recipients per day

That gap between 10,000 and 300 catches people out constantly. If you’re prospecting from a free Outlook.com address, you have a fraction of the headroom you think you do.

Exceed the cap and you could get:

• •

  Our daily message limit was meant to stop spammers–we’re sorry that it’s getting in your way. You can wait a day to send your message.

Yahoo! Mail

Yahoo Mail is a web-based email app for desktop and mobile, with document and image storage, travel confirmations, and package tracking built in.

Sending limits, approximately:

• •

  100 emails per hour

• •

  500 emails per day

• •

  100 recipients

Yahoo doesn’t publish exact figures, deliberately, because vague limits are harder for spammers to game. Exceed them and you’ll get a notification telling you how long to wait before sending again.

Proton Mail

Proton Mail is a private email service built on open source, independently audited end-to-end encryption and zero-access encryption.

Sending limits:

• •

  150 emails per day on free plans

• •

  Unlimited messages on the Proton Unlimited plan

Exceed them and you could see:

• •

  You are temporarily banned from sending because of spammy or undeliverable emails

Zoho CRM

Zoho CRM is a cloud-based platform for tracking leads, automating sales workflows, and generating invoices, with integrations into 500+ third-party apps.

Sending limits by plan:

• •

  Free: 150 emails per day

• •

  Standard: 250 emails per day

• •

  Professional: 500 emails per day

• •

  Enterprise: 1,000 emails per day

• •

  Ultimate: 2,000 emails per day

Exceed them and you could get:

• •

  Error (5.4.6 Mail rate exceeded)

GMX

GMX is a multi-service provider, and free email accounts are one piece of what it offers.

It doesn’t publish a numeric daily cap. It runs Spamhaus filtering instead.

Get flagged as spam and you’ll receive a warning in your inbox. GMX publishes a list of recommendations for getting unflagged.

AOL Mail

AOL Mail is a free web-based email service from AOL, a division of Yahoo! Inc.

Sending limits, approximately:

• •

  100 recipients per message

• •

  500 recipients per connection

AOL doesn’t disclose exact numbers either. Exceed the limit and you’ll get a notification with a waiting time.

How many emails you should actually send

Having the capacity to send thousands a day doesn’t mean using it serves you. I can also sit on the couch watching TV all day. Doesn’t mean it’s a plan.

Here’s the ramp we recommend at lemlist, which is also the schedule lemwarm automates for you:

1. 1.

   Weeks 1–3: start at 10–20 emails per day on a fresh inbox

2. 2.

   Week 4: work up to around 100 emails per day

3. 3.

   After a full warm-up: 150–200 emails per day, at the top end

Treat 100 a day as your working default. The 150–200 range is a ceiling you earn after a complete ramp-up, not a starting point. These are our numbers based on what we see across lemlist accounts, not a rule any provider publishes.

I don’t recommend going past that. Not every email gets opened, answered, or even delivered, and every bounced address chips away at your sender reputation. Slow and steady gives you room to stop, check the data, and fix problems while they’re still small.

Verifying every address before you send is non-negotiable here. Bounces are the fastest way to undo a warm-up.

How many sending inboxes do you actually need for cold email?

Worth clearing up first: an email account and an email address are different things. One account (one Google Workspace seat, say) can carry several addresses through aliases, but aliases share the same sending reputation and count against the same daily quota. Google explicitly counts messages sent from alternate addresses and aliases toward the user’s limit. Aliases buy you nothing in volume.

Separate inboxes are what buy you headroom.

The maths is simple. If 100 emails a day is your safe default per inbox and you need 400 a day in pipeline, you need four warmed inboxes, ideally spread across more than one domain. One inbox on one domain means a single point of failure: one bad list, one spike in complaints, and everything stops.

A reasonable setup for most teams:

• •

  Solo founder or one rep: 1–2 inboxes on a secondary domain, 100–200 emails/day total

• •

  Small outbound team: 1–2 inboxes per rep, each on a warmed sending domain

• •

  Scaling team: multiple domains, several inboxes per domain, rotation handled automatically

Managing that by hand is where it falls apart. lemlist’s inbox delivery hub rotates sends across all your connected inboxes and domains automatically, so volume spreads instead of piling onto one address.

How to respect sending limits without babysitting your campaigns

The practical answer is a sending schedule.

With a cold email tool, you set it once and emails spread across the day rather than going out as one blast. Aim for around 100 a day per inbox, distributed, so the pattern looks like a person sending email rather than a machine emptying a queue.

For scheduling, stick to these:

• •

  Respect the weekends

• •

  Choose timeframes that match your target audience’s working hours

• •

  Keep each inbox at 100 emails a day as the default

• •

  Leave gaps between sends so you’re never firing several emails at the same second

Email algorithms are tricky, and more spammers show up every day, so providers have made protecting recipients their main job. It pays to be sensible about your campaigns.

Sending 300 emails in one day for a terrible response rate will damage your domain. That’s the whole trade.

Two lemlist features remove the manual guesswork here. lemwarm is included in every seat and runs the warm-up ramp in the background, building inbox reputation before your real campaigns start. The Deliverability Hub handles inbox rotation, time-zone-based sending, and provider matching, so your sends land during working hours for the recipient and go out from an inbox that suits the recipient’s provider. You set the ceiling once and the system keeps you under it.

If you want to tune the numbers yourself, the lemlist academy shows you how to set email limits with lemlist.

And before any campaign goes live, run through a proper deliverability checklist so nothing in the setup is quietly working against you.

Stop treating email as your only channel

Here’s the uncomfortable part of this whole topic.

If your entire pipeline depends on email, your provider’s daily cap is also your pipeline cap. You can add inboxes and domains to push that ceiling higher, and you should. But you’re still playing one game, on one surface, where the rules get stricter every year.

Multichannel breaks the dependency. A sequence that pairs email with a LinkedIn connection request, a call, an SMS, or a WhatsApp message reaches the same prospect several ways without adding a single email to your daily count. Prospects who ignore email answer on LinkedIn. Prospects who ignore both pick up the phone.

lemlist’s multichannel prospecting runs all of it from one sequence, with conditional steps so the next action depends on what the prospect actually did. Sending limits stop being the ceiling on your pipeline and go back to being what they always were: a constraint on one channel.

Common mistakes to avoid

Sending everything from one domain. One complaint spike and your whole operation stops. Spread volume across multiple inboxes and domains with automatic rotation in the inbox delivery hub.

Skipping warm-up. A brand new mailbox sending 100 cold emails on day one is the most obvious spam pattern there is. lemwarm ramps new inboxes gradually, and it’s included in every lemlist seat.

Ignoring DMARC. SPF and DKIM alone no longer clear the bar at Gmail, Yahoo, or Outlook if you’re sending at volume. Publish a DMARC record at minimum p=none. lemlist’s deliverability setup handles the configuration.

Blasting instead of spacing. Two hundred emails sent in ten minutes reads as automation to every filter in the chain. Spread sends across working hours.

Flying blind on reputation. Most people discover a deliverability problem from a dead pipeline three weeks later. Monitoring and alerts flags reputation drops, blacklist hits, and authentication breaks while you can still fix them.

Over to you

If you remember one number from this page, make it 100. That’s your default per inbox per day, regardless of what your provider technically allows. Everything else is scaffolding around it: warm up before you ramp, authenticate before you scale, rotate across inboxes instead of pushing one harder, and add channels so email volume stops being your pipeline ceiling.

lemlist is rated 4.6/5 from 2,000+ reviews on G2 and other platforms, and lemwarm comes with every seat, so the warm-up and the rotation run whether or not you remember to think about them.

Set your limits once, let the system hold them, and go write better emails.

Start a 14-day free trial