This guide shows you how to set (and scale) safe email sending limits in lemlist for Gmail/Google Workspace and custom SMTP accountsâso you can protect deliverability while still hitting your volume goals.
Learning Objective
By the end of this tutorial, youâll know how to configure your daily sending limits in lemlist, choose a safe starting quota, and scale volume without harming your domain reputation.
Why This Matters
Sending limits help you control daily volume and reduce the risk of provider restrictions, spam placement, or account issues. A steady, gradual ramp-up typically performs better than sending large volumes too quickly.
Prerequisites
You have at least one sending email address connected to lemlist (Gmail/Google Workspace or SMTP).
You know which address (or team address) you want to apply limits to.
Core Lesson â Step-by-Step Workflow
Phase 1: Choose a safe daily sending limit
If you use Gmail/Google Workspace: Google has theoretical sending limits (you can review them here and here), but for consistent cold outreach performance, we recommend being more conservative than the provider maximums:
New mailbox (< 1 year old): for optimal results, we strongly recommend not going over 40 emails/day per inbox.
If you keep lemwarm as your reputation âsignalâ and use warm-up + lemlist: a typical safe range is 60â70 emails/day per inbox (as long as deliverability signals stay healthy).
If you use a custom SMTP inbox: follow your providerâs recommendation. If you donât have a clear guideline, start conservatively (especially for new mailboxes) and scale gradually based on performance and deliverability signals (bounces, replies, spam complaints). As a rule of thumb, avoid going over 40 emails/day on a new (< 1 year) mailbox, and only increase once your signals are stable.
Phase 2: Set (or adjust) sending limits in lemlist
Open your avatar/profile menu, then go to Settings.
In the left sidebar, click Sending limits, choose the sending email address you want to edit, then set your preferred daily email limit.
Important
Changes are saved automaticallyâso double-check your final number before leaving the page.
Even with correct limits in lemlist, providers (like Google) can still restrict sending based on their own reputation and policy signals.
Phase 3: Scale volume safely
Monitor performance proactively. lemlist can pause sending when it detects you may exceed your quota, but itâs not foolproofâkeep an eye on total daily volume and campaign settings.
If you need higher volume, scale horizontally. Instead of increasing one inbox aggressively, add more sending addresses and distribute sending (this is typically safer for deliverability than pushing one inbox to its max).
Practical Application / Real-Life Example
Example scaling plan (per inbox):
New mailbox (< 1 year): aim for 20â40 emails/day while you validate performance (bounces, replies, spam signals).
If you keep lemwarm as signal and run warm-up + lemlist: you can typically move to 60â70 emails/day if metrics stay healthy.
Need 300 emails/day? Use 4â6 inboxes with conservative limits rather than pushing a single inbox hard.
Troubleshooting & Pitfalls
Issue: My emails still get blocked/throttled even with a low limit
Root cause: Provider reputation algorithms can restrict sending based on your inbox/domain history, content, bounces, or engagement.
Fix: Reduce volume further, improve targeting to reduce bounces, and scale more gradually.
Issue: Iâm sending more than expected
Root cause: Multiple campaigns/inboxes or an alias setup can make volume harder to track.
Fix: Audit which inboxes are active, confirm the correct sending address is selected in Sending limits, and verify any alias provider restrictions.
Issue: Sending pauses unexpectedly
Root cause: lemlist may pause sending when it detects you might exceed your quota, or your provider may be enforcing additional restrictions.
Fix: Lower the daily limit and resume with a slower ramp-up.