TL;DR
If Google or lemlist pauses your sending: Reduce daily volume (Settings → Sending limits — a new mailbox sends 30–40 emails/day through lemlist, and total output including lemwarm and manual replies stays under 70/day per provider), set up a custom tracking domain (Settings → Custom tracking domain), disable open tracking on short emails (Campaign Settings → Tracking), and verify DNS records (SPF/DKIM configured). Use Google Workspace (not free Gmail), and after a pause or a flag, restart at about 15/day with a ramp increment of 3 rather than resuming at your old volume. Test with a small batch — if it delivers without warnings, the issue is resolved.
Symptoms
Warning email from lemlist about unusual activity or temporary pause
Google rejects emails with "blocked" status in logs
Emails stop sending despite leads launched and scheduled correctly
Sudden drop in deliverability or spike in bounce rate
Account automatically blocked after second flag from lemlist monitoring
Environment
Applies to:
Users sending cold email via lemlist using Google Workspace or Gmail
New senders ramping up volume quickly
Users with free/trial Google accounts
Accounts with high send rates, no custom tracking domain, or missing DNS records
Step-by-Step Fix
1. Reduce daily sending volume
Go to Settings → Sending limits
A new mailbox sends a maximum of 30–40 emails/day through lemlist. Open at 30, and only move to 40 once a month of clean sending is behind it.
Your total output — lemlist + lemwarm + manual replies — stays under 70/day per provider in every case. If you keep lemwarm at 10/day as your reputation signal, a settled mailbox sits around 40–50/day total, which leaves room for the replies you write by hand.
The ceiling is per provider, not per mailbox: six Google mailboxes share one Google-side reputation, not six independent budgets. Adding mailboxes will not get you around a Google-side block.
✅ Verify: Check Settings → Sending limits — daily quota below limit, schedule doesn't exceed it
2. Set up a custom tracking domain
Go to Settings → Custom tracking domain
Add subdomain (e.g., links.yourdomain.com)
Create DNS records at your domain provider:
CNAME record pointing to lemlist
Wait for DNS propagation (up to 24 hours)
Verify in lemlist
✅ Verify: Custom tracking domain shows Active status, link tracking works
3. Disable open tracking for short emails
For one-sentence or very short emails:
Go to Campaign Settings → Tracking
Toggle "Track opens" OFF for short email steps
Prevents tracking pixel flagging spam filters
✅ Verify: Toggle is grey/off, short emails deliver normally
4. Use a professional domain with proper DNS
Switch from free Gmail:
Don't send from
@gmail.comUse Google Workspace with a custom domain
Configure DNS records:
Verify SPF record is configured correctly
Verify DKIM record is configured correctly
Add DMARC record
SPF, DKIM and DMARC together carry the largest single share of your warm-up score, so broken DNS caps the score no matter how well the mailbox sends.
Check DNS at your domain registrar or use MXToolbox
✅ Verify: DNS tools show SPF and DKIM as valid, test emails reach inbox
5. Restart volume the way a recovering mailbox should
A mailbox that was flagged, blocked, or paused for more than 7 days does not resume at its previous volume. It goes back through a short ramp first.
After an incident:
Restart at about 15/day in lemlist + 15/day in lemwarm — roughly 30/day total
Use a ramp increment of 3, not 1. A mailbox rebuilding trust is not a new mailbox
Keep both reputation signals running until it is stable again: inbox placement tests and lemwarm
Climb back toward 30–40/day only once signals hold
If the domain itself is brand new: keep the whole domain under 100 emails/day across every mailbox on it combined for the first month.
Avoid trial accounts:
Don't send from the Google Workspace free trial
Wait until the account is fully activated and paid
✅ Verify: Campaign reports show a gradual volume increase, no warnings
6. Send clean, compliant content
Avoid spam triggers:
No excessive formatting
Limit images
Avoid spam words ("FREE", "Act now", etc.)
Include required elements:
Physical address in footer
Unsubscribe option (reply with "unsubscribe" or link)
Use proper list hygiene:
Send only to engaged, opted-in recipients
Remove bounces immediately
✅ Verify: Spam testing tools show low scores, normal open rates
Confirm It's Fixed
✓ Campaign schedule within recommended limits, not exceeding quota
✓ Custom tracking domain shows Active, link clicks tracked
✓ Open tracking disabled on short emails, deliverability improved
✓ SPF and DKIM validate successfully, test emails land in inbox
✓ Volume restarted at ~15/day and climbed gradually without new warnings or blocks
✓ A reputation signal is in place — inbox placement 1–2 per month, or lemwarm at 10/day
✓ Content complies with best practices, recipients can unsubscribe
✓ No warning emails from lemlist or Google
Why It Happens
Google flags accounts for unusual sending patterns: sudden volume spikes, high bounce rates, missing authentication, or spam-like content. lemlist's monitoring system pauses accounts with risky activity to protect community deliverability.
Prevent this: Maintain consistent sending cadence, respect the caps (30–40/day through lemlist on a new mailbox, under 70/day total per provider), use a custom tracking domain, authenticate with SPF/DKIM/DMARC, avoid free/trial accounts, keep one reputation signal running at all times, and never resume a paused mailbox at its old volume. Low and stable beats high and aggressive: between two numbers inside the range, take the lower one.
Alternatives
Inbox rotation — Spread volume across multiple Google Workspace accounts using lemlist's inbox rotation feature, remembering that mailboxes on the same provider share one reputation budget rather than each getting a fresh one
Multiple domains — Agencies and high-volume senders can use several warmed-up domains to scale safely, each with its own full ramp-up and 14-day stabilization
Email warm-up — Use lemwarm to build domain reputation before scaling, and keep it at 10/day afterwards as your early-warning signal


