Gmail sending limits, and a warm-up that respects them

Google publishes two daily send limits: 500 messages a day from a personal Gmail account, and 2,000 a day from a Google Workspace account. Both are counted over a rolling 24 hours, not reset at midnight, and hitting either one locks sending for up to a day.

What the two limits actually are

Google states the numbers itself, and they are worth reading from the source rather than from a blog, because the details around them move. A personal @gmail.com account is allowed 500 messages in a rolling 24-hour period. A Workspace account, on a paid plan and past its trial, is allowed 2,000. Trial and recently created Workspace accounts sit lower until Google lifts them. Separate limits govern how many recipients one message may carry, and Google's own tables are the place to read those.

• Limits for sending and getting mail, for personal Gmail accounts.
• Gmail sending limits in Google Workspace, for everyone else.

Exceed the limit and Gmail stops accepting new messages from that account for up to 24 hours. Nothing already delivered is undone, and nothing is deleted. You simply cannot send, which on the day you are chasing a deadline is its own kind of expensive.

Why the ceiling is the wrong number to plan against

A daily limit is a ceiling on volume. It says nothing about whether the mail lands in an inbox or in spam, and those are decided by different machinery. Spam filtering reads the pattern of your sending against what your address has done before. An address that has sent twenty personal messages a day for two years and then sends four hundred in one afternoon has changed its behaviour completely, and there is no way for a filter to tell that apart from a compromised account, which is the exact thing it exists to catch.

This is the trap in the published numbers. They read as permission. A sender who treats 500 as an allowance to spend rather than a wall to stay away from gets filtered long before they get blocked, and filtering is the more expensive failure: blocking tells you it happened, and spam foldering does not.

A ramp that a filter reads as growth

The shape you want is a small number that increases at a steady rate, so today looks like yesterday plus a little. Onmindo starts a new account at twenty messages a day and adds twenty a day, and the cap is enforced by the server rather than suggested in a help article. A send that would cross the cap is refused, not warned about.

Two weeks in, the cap is 280 a day, and on day 25 it reaches 500 and stops there. 500 is a personal Gmail account's own ceiling, so the ramp never asks Google for more than Google allows. What the shape buys you is that every day is a believable step from the one before it, which is the thing a filter is reading while your address has no history to go on.

Pacing matters as much as volume

A hundred messages leaving in ninety seconds and a hundred messages leaving over four hours are the same number and two completely different signals. Onmindo puts thirty to a hundred and eighty seconds of jitter between messages in a bulk send, so the gaps are uneven the way a person's are. A perfectly regular interval is its own tell: nobody types at exactly one message every forty seconds for an hour.

The tracking domain has its own clock

A domain that was registered last week and is now rewriting every link in your mail is the shape of a phishing campaign, and it is scored as one. Onmindo blocks click tracking on bulk sends until the tracking domain is about fourteen days old, and leaves click tracking off by default in any case. Open tracking is unaffected: it is the link rewriting that carries the risk.

The practical consequence is worth planning around. Stand your account up two weeks before you need it, let the domain age while you are doing something else, and the first campaign starts from a warm domain rather than a cold one. There is no way to buy that fortnight back later.

What to do the week before a real send

1. Create the account and send normal mail from it for a fortnight at the ramp's own pace. Ordinary one-to-one mail is the best warm-up traffic there is, because it is the traffic filters want to see.
2. Check the daily cap in the dashboard before planning a batch. It shows today's count and today's ceiling, so the number you plan against is the real one.
3. Put a visible opt-out in anything going to more than a handful of people. Onmindo refuses a bulk send without one, which is deliberate: a missing unsubscribe is the single easiest complaint to earn.
4. Keep the list small and warm before you make it large. A hundred people who know who you are beat a thousand who do not, on delivery as well as on replies.

What none of this fixes

A warm-up buys a sending pattern that looks legitimate. It does not buy you a reader. Bad mail sent slowly from a warm domain is still bad mail, and the complaint rate it earns will undo a fortnight of careful ramping in an afternoon. The guardrails are there so that the mail worth sending arrives, not so that more of it can be sent.

Onmindo enforces the cap, the jitter, the domain age and the opt-out rule on every account, with nothing to configure and no way to turn them off. See what else it refuses to guess about.