If your outreach emails suddenly stopped working after years of no problems, here's what happened and how to fix it.
I recently worked with a client who's been sending professional outreach emails for over a decade. She's a well-established freelancer in her industry — not a spammer, not a marketer running shady campaigns. She sends a few hundred personalized emails a few times a year to professional contacts who know her and expect to hear from her.
It had always worked fine. Then, in late December 2025, it stopped.
Her emails started bouncing with a "Message blocked" error. She'd get through 10, maybe 60, then Gmail would shut her down. She tried sending in tiny batches — three here, seven there, spaced out over two days. Still blocked. She had a colleague set up a second Gmail account as a workaround. It worked for a few weeks, then got blocked too.
She was understandably frustrated. Nothing about her process had changed. She even wondered if a specific word in her subject line had triggered it. It hadn't.
In November 2025, Google changed how it enforces its email sending policies. The rules themselves weren't entirely new — Google had been rolling out stricter requirements for bulk senders since February 2024. But the enforcement changed dramatically. Where Gmail used to rate-limit or quietly flag messages that looked like bulk sends from personal accounts, it now permanently rejects them with a 5.7.1 error code. No warning, no retry, just a bounce.
My client's first bounce was December 30, 2025 — right after the enforcement change took effect. That's not a coincidence.
Here's the thing: to a human, her emails are clearly legitimate professional correspondence. To Gmail's automated filters, they look like this:
Same subject line across every message in a sending session. She was pitching the same program to hundreds of contacts, so naturally the subject was identical.
Near-identical body text. She composed a detailed pitch — think press release style with scheduling information, program descriptions, and broadcast details — and copy-pasted it to each recipient, sometimes adding a personal greeting, sometimes not.
Links in every email. Each message contained a link to her organization's website, and some included a shortened URL (TinyURL) pointing to an audio file. URL shorteners are a major red flag for spam filters because they're heavily used by phishers to mask malicious destinations.
Embedded image. At least one of her email templates included an inline image, which further matched the "marketing email" fingerprint.
Sent through Apple Mail via Gmail SMTP. She was composing in Apple Mail on her Mac, which connects to Gmail's SMTP servers to send. The authentication was fine — proper OAuth, modern setup, nothing misconfigured. But she was essentially running a bulk email campaign through a channel Gmail now reserves for personal communication.
Any one of these signals might not trigger a block. Together, they paint a picture Gmail's outbound filter is specifically trained to catch.
This is the part that's most frustrating for people in this situation. Nothing they changed caused the problem. Gmail changed.
Google's decision to start permanently rejecting non-compliant outbound messages (rather than just flagging or throttling them) flipped a switch for countless legitimate senders who'd been operating in a gray area for years. If you're a freelancer, consultant, nonprofit organizer, or anyone else who sends professional outreach through a personal Gmail account, you may have already hit this wall — or you're about to.
The second account getting blocked confirmed the diagnosis. Gmail wasn't penalizing a specific account; it was recognizing the pattern — same computer, same IP address, same Apple Mail client, same content structure — and applying the same rules regardless of which @gmail.com address was sending.
My client was actually experiencing two distinct issues that she understandably conflated:
"Message blocked / Message rejected" (Status 5.7.1) — This is Gmail's outbound content filter permanently rejecting a message before it ever reaches the recipient. The message leaves Apple Mail, hits Gmail's servers, gets scanned, and gets bounced back. This is the enforcement change in action.
"Cannot Send With This Server" — This is an Apple Mail error that fires before the message leaves the computer. It means Gmail has temporarily suspended the account's ability to submit messages via SMTP. Think of it as Gmail pulling the plug on the pipeline after detecting too many flagged sends. The account still works in a web browser, but Apple Mail can't connect.
The first error came first on her original account, which is what prompted creating the second account as a workaround.
The test-and-debug approach — sending carefully controlled batches with different variables to isolate the trigger — is technically thorough but practically burdensome for someone who just needs to get back to work. Once you understand the root cause (Gmail's enforcement changed, and personal Gmail isn't the right channel for this type of sending), the fix becomes clear.
If you're sending on behalf of an organization — pitching their programs, distributing their content, marketing their services — the most natural fix is to send from that organization's email domain. Their domain has established reputation, proper authentication (DKIM, SPF, DMARC), and is recognized by receiving mail servers as a legitimate source.
This is the cleanest solution if you can get it. It's worth asking, even as a freelancer or contractor — it's in the organization's interest for their outreach to actually reach people.
For about $7 a month, Google Workspace gives you a custom domain ([email protected]), a 2,000 email per day sending limit, proper email authentication you control, and your own sender reputation — separate from the shared pool of free Gmail users.
That shared pool is part of the problem. When you send from @gmail.com, your reputation is tangled up with millions of other accounts, including spammers. Google protects the gmail.com domain by aggressively throttling individual users who look like they might be sending bulk mail. With your own domain, you control your own reputation.
The setup requires some technical knowledge — DNS records, DKIM keys, SPF and DMARC configuration — but it's a one-time setup that a tech-savvy friend or consultant can handle in an afternoon.
Tools like YAMM (Yet Another Mail Merge, $25/year) or Mailmeteor plug into Gmail and handle the sending through Gmail's API rather than raw SMTP submission. They throttle automatically, manage sends from a spreadsheet, and add proper headers that tell Gmail "this is a legitimate mail merge." This alone may resolve the blocks because the sending path is handled differently than composing and sending individual messages through Apple Mail.
This is the fastest fix — you can be up and running the same day — and it works as a bridge while you sort out a longer-term solution.
Remove shortened URLs immediately. If you're using TinyURL, Bitly, or any other link shortener in your outreach emails, replace them with direct links. Shortened URLs are one of the strongest spam signals in outbound email filtering.
Stop sending bulk email through Apple Mail. Even with perfect authentication, Apple Mail's SMTP submission path isn't designed for high-volume sends. Use Gmail's web interface at minimum, or a proper sending tool.
Vary your subject lines. Even small variations ("For WXYZ: New Season of [Program]" vs. the same subject for everyone) reduce the content-similarity signal.
Add real personalization. A genuine first sentence that references something specific about the recipient makes each message distinct in Gmail's content fingerprinting.
Google's November 2025 enforcement change isn't going away. If anything, the trend across all major email providers (Google, Microsoft, Yahoo) is toward stricter authentication requirements, lower tolerance for bulk-like patterns from personal accounts, and permanent rejection rather than quiet filtering.
If your work involves sending more than a handful of similar emails to professional contacts, the era of doing that through a personal Gmail account is effectively over. The good news is that the alternatives are affordable, accessible, and in many cases make your outreach more professional and more likely to land in inboxes.
The irony in my client's case: she's an award-winning professional with decades of credibility in her industry, sending to contacts who genuinely want to hear from her. Gmail doesn't know that — it only sees the pattern. The fix isn't to change who she is or what she's sending. It's to send it through a channel that matches the scale and style of what she's doing.
Joe Skelley is an independent tech support consultant based in St. Paul, Minnesota. He helps small businesses and solo practitioners adapt technology to fit their work. You can reach him at joestechsupport.com.