Can I send a mass email from Gmail?
Yes, within limits, and the limits differ by account type. These are Google's published figures — treat them as the ceiling, not a target, and check Google's own documentation before relying on an exact number, since they are revised periodically.
| Account | Recipients per day | Notes |
|---|---|---|
| Free @gmail.com | 500 | Counted per recipient, not per message |
| Google Workspace | 2,000 external | Higher internal allowance |
| Workspace multi-send | Lower, plan-dependent | Not on every tier; unavailable on free Gmail |
| Any account, new | Effectively much lower | Reputation is built over weeks |
Not the daily cap — almost nobody sends 500 real emails a day. It is the rate limit and the spam classifier, both of which react to a burst of near-identical messages from an account that has never done that before. Hitting either can lock sending for up to 24 hours.
The three ways to do it, ranked
1. BCC — do not
One message, everyone hidden in BCC. It is the fastest method and the worst outcome: identical content, no personalisation, no name in the greeting, and a recipient pattern that reads as bulk to every filter in the chain. For outreach that needs a reply, this is close to guaranteed failure.
2. Mail merge — better, still one-size
Workspace's multi-send, or an add-on driven by Google Sheets, sends a separate message per recipient with fields swapped in. Each arrives as an individual email, which is a real improvement.
- Good for: newsletters, announcements, anything where the same message genuinely applies to everyone.
- Weak for: job outreach.
Hi {{FirstName}}is not personalisation — the body is still identical, and the reader can tell. - Watch: a merge field that fails renders literally.
Hi {{FirstName}},in a real inbox ends the conversation.
3. Many individual emails, sent on a schedule
Each message written for its recipient, sent minutes apart across the working day, from your own account. Slower, and the only approach that behaves like what it is. This is what job-search outreach should be: 15 real emails beat 200 merged ones, and there is no version of the merged 200 that gets replies.
Why bulk sends land in spam
| Trigger | What to do |
|---|---|
| Unverified addresses bouncing | Verify before sending — this is the biggest single factor |
| Burst of sends in minutes | Space them out; minutes apart, not seconds |
| Identical body across recipients | Vary the substance, not just the name |
| Attachment to an unknown recipient | Link instead on first contact |
| New account, sudden volume | Ramp over weeks; start at 10–20/day |
| Link-heavy or tracking-pixel-heavy body | One link. Skip open tracking for job outreach |
A guessed address that does not exist is a hard bounce recorded against your sending reputation. Enough of them and mail to valid recipients starts going to spam too. Verifying an address costs a moment; recovering a reputation takes weeks.
A workable daily pattern for job outreach
- Build the list — named people at named companies, not role inboxes.
- Verify every address before it enters the send queue.
- Write each message; reuse structure, not sentences.
- Schedule 10–25 a day, a couple of minutes apart, in the recipient's morning.
- Queue one follow-up per contact, three to five working days out.
- Stop sending to anyone who replies — including the follow-up.
This pattern, without the spreadsheet
Apply Ops sends from your own Gmail account: verified addresses, drafts built from your resume, timezone-aware scheduling with a daily cap, and one automatic follow-up per contact that is cancelled if they reply.
See scheduled Gmail outreach