New Feature Release: Fixed-Stage Email Warmup for Sending Domains

Modified on Wed, 4 Jun at 12:28 PM

We’re excited to introduce a built-in 
Fixed-Stage Domain Warmup 
system to help you improve email deliverability and protect your sender reputation—especially when using new or unseasoned domains.
Important: This feature is being rolled out in Laps(Beta Program). You’ll need to manually enable it to start using warmup for your domains.


image

What’s New

  • Automatic warmup for newly created domains
  • Manual warmup activation for existing domains
  • Smart warmup stage recommendation based on past sending activity and Google Postmaster data
  • Fixed daily sending limits to ensure safe ramp-up
  • Full support for both agencies and sub-accounts LeadConnector Email Sending domains
How It Works
This warmup system uses a 
fixed-stage model
:
  • Each stage has a daily sending limit.
  • You'll progress to the next stage only after reaching the current day's limit.
  • No hourly caps are enforced.
  • Emails must be sent through the warming domain to move forward.
  • Warmup automatically pauses once the daily limit is hit, and resumes the next day.

NoteDuring this initial phase, sending above the stage limit is allowed and emails will not be blocked. However, future updates will strictly enforce these limits and block excess sends once the cap is reached.


How to Enable Warmup


For Newly Created Domains:
Warmup is enabled automatically after domain creation and verification.
For Existing Domains:
You can enable warmup manually from the following locations:
Account Settings:
Settings → Email Services → SMTP Service → Dedicated Domain and IP
When enabling warmup on existing domains, the system will recommend a starting stage based on historical email activity and available Google Postmaster data.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article