TL;DR: Find the exact pause message in Warm up, fix the matching issue in your email provider or DNS, then click Start in Warm up to resume. Verify the mailbox stays active and new warm-up emails are no longer rejected.
Symptoms
lemwarm shows as paused or stopped in Warm up.
You see messages like “lemwarm has been disabled because one of the email we sent was rejected by the recipient”.
You see messages like “lemwarm was disabled as your emails are rejected by recipients. Please verify your MX, DMARC, SPF records.”
You see messages like “lemwarm has been paused as your DNS has errors”.
You see messages like “lemwarm was disabled as your email provider does not allow external forwarding”.
You see messages like “lemwarm was disabled as your domain fails SPF record verification”.
Environment
Applies to mailboxes using lemwarm.
Applies to Google Workspace, Microsoft 365, and custom SMTP setups.
Some pauses are stricter if you are not using a Custom Tracking Domain (CTD).
Step-by-Step Fix
Open the paused mailbox in Warm up.
Check the exact pause reason shown for the mailbox.
✅ Verify: You can read the full error message before making changes.
Match the message to the correct fix.
Use the table below and follow only the row that matches your error.
Error or pause message | What it means | What to do |
“lemwarm has been paused as your DNS has errors” | Your DNS check failed. | Check your MX, SPF, DMARC, and CTD records. Fix any missing or invalid record, then recheck DNS. |
“lemwarm was disabled as your domain fails SPF record verification” | Your sender domain fails SPF. | Update the SPF TXT record so it includes your real sending server or sending IP. |
“lemwarm was disabled as your domain fails DKIM or SPF verification” | Your domain authentication is incomplete or invalid. | Check DKIM, SPF, and DMARC. Correct invalid public keys or missing DNS values. |
“lemwarm was disabled as your email provider does not sign your outbound emails and they are rejected by DMARC policies by the recipients” | Your provider is sending unsigned mail. | Enable outbound signing and verify DKIM, SPF, and DMARC with your provider. |
“lemwarm was disabled as your emails are rejected by recipients. Please verify your MX, DMARC, SPF records.” | The recipient server is rejecting your mail because of domain or policy issues. | Check MX, SPF, DKIM, and DMARC. Also review transport rules or provider filtering that may block outgoing mail. |
“lemwarm was disabled as your sender domain was not found. Please verify your domain configuration” | Your sending domain does not resolve correctly. | Fix the domain DNS zone and confirm the domain exists and resolves publicly. |
“lemwarm was disabled as your domains was unable to be resolved. Please verify your DNS records” | The recipient could not resolve your sender domain. | Check public DNS resolution for the sending domain and correct broken DNS records. |
“Lemwarm was disabled as your email provider reported a valid domain as not found. Please check with your email provider and restart lemwarm.” | Your provider reported a false domain-not-found error. | Contact your email provider and ask why it rejected a valid sender domain. |
“lemwarm has been disabled as your antispam software has rejected too much incoming lemwarm emails as spam before they can reach your inbox” | Your inbound filtering is blocking lemwarm emails. | Check inbound filtering, SPF, and DMARC. Allow lemwarm emails to reach the inbox. |
“You're using mailchannels.net and it detected lemwarm emails are spam. We are pausing your lemwarm so community is not affected.” | MailChannels is blocking warm-up emails. | Disable or relax MailChannels filtering for lemwarm traffic. |
“lemwarm was disabled as the use of antispam software mailinblack is incompatible with the use of lemwarm” | Mailinblack blocks warm-up traffic. | Disable Mailinblack for the mailbox or stop using lemwarm on that mailbox. |
“lemwarm was paused as an email was blocked by a spam filter” | Your provider or the recipient blocked the message as spam. | Review sending restrictions, anti-spam rules, and provider policy. If you use a custom domain, fix reputation and authentication before restarting. |
“lemwarm has been disabled because one of the email we sent was rejected by the recipient” | A recipient-side bounce triggered a pause. | Read the bounce reason in full. Most cases are caused by DNS, forwarding, spam filtering, or a non-existent mailbox. |
“lemwarm was disabled as your email provider does not allow external forwarding” | Your mailbox or organization blocks forwarding. | Ask your admin to allow external forwarding or remove the forwarding rule that rejects incoming warm-up emails. |
“lemwarm has been disabled because one of the email we sent was rejected by the recipient” with error 550 5.7.520 Access denied | Forwarding or transport rules blocked the email. | Ask your admin to review filtering rules and transport rules for the mailbox. |
“Your email provider blocked a lemwarm email with the reason ‘blocked permanently due to successive mailings’. Your email provider is therefore incompatible with lemwarm.” | Your provider or filter rejects warm-up patterns. | Check provider filtering and anti-spam settings. If the provider cannot allow warm-up traffic, that mailbox is not compatible with lemwarm. |
“lemwarm was disabled as your email account does not exists anymore” | The mailbox no longer exists. | Reconnect a valid mailbox or fix the mailbox with your provider. |
“lemwarm was disabled as your mailbox is replying with bounce messages. Please check your email configuration (forwarding, etc.)” | The mailbox is misconfigured or bouncing incoming mail. | Check forwarding rules, mailbox status, and auto-routing settings. |
“lemwarm was disabled as your email account is over quota” | The mailbox is full or restricted. | Free mailbox space or remove the receiving restriction, then test incoming mail again. |
“lemwarm was disabled as your email service provider is not reachable” | Your provider had connectivity or MX issues. | Check whether the domain can receive email and verify the MX record with your provider. |
“lemwarm has been paused as several emails were rejected from your email provider. Last reason was” | Your provider rejected multiple sends before delivery. | Run a DNS check on the sending domain and ask your provider why outbound mail is being rejected. |
“lemwarm has been disabled because one of the email we sent was rejected by the recipient” with low reputation errors | Your domain reputation is too low. | Warm up a healthier domain, reduce risky sending, and consider switching to a new domain if the reputation is already damaged. |
“lemwarm was disabled as your domain is listed on https://spamrl.com/” | Your domain is listed on SpamRats/SpamRL. | Request delisting or use a new domain. |
“lemwarm was disabled as your domain is listed on https://www.spamcop.net/” | Your domain is listed on SpamCop. | Request delisting or use a new domain. |
“lemwarm was disabled as your emails are rejected by recipients for DMARC reason” | Your DMARC policy is invalid or too restrictive. | Review the DMARC TXT record and correct invalid syntax or an overly strict policy. |
“Your mail server rejected an email that was using a valid DMARC record. Please check that your mail server is properly configured before restarting lemwarm.” | Your server rejected a valid DMARC sender incorrectly. | Check your mail server policy and ask your provider why it rejected a valid DMARC-aligned email. |
Apply the fix in your email provider or DNS.
Do not restart lemwarm before the underlying issue is corrected.
✅ Verify: Test email sending and receiving works outside lemwarm.If you do not use a Custom Tracking Domain, set one up.
Without a CTD, lemwarm may pause after a single anti-spam bounce. With a CTD, lemwarm is more tolerant of temporary filtering issues.
✅ Verify: Your sending setup shows an active custom tracking domain.Restart lemwarm.
Go back to Warm up and click Start.
✅ Verify: The mailbox status changes from paused to active.
Confirm It's Fixed
✓ The mailbox shows as active in Warm up.
✓ New warm-up emails are no longer rejected or bounced.
✓ Test emails send and receive normally from the mailbox.
✓ DNS checks for MX, SPF, DKIM, and DMARC return valid results.
Why It Happens
lemwarm pauses a mailbox when bounces, spam filtering, DNS errors, forwarding restrictions, provider limits, or reputation issues make warm-up unsafe. Prevent this by keeping domain authentication valid, allowing warm-up emails through filters, and using a CTD.
Alternatives
If you cannot edit DNS, ask your IT team or DNS admin to update the records.
If your provider blocks warm-up traffic by policy, use another mailbox or a different domain.
If your domain reputation is too low, move warm-up to a new sending domain.
Escalate If Unresolved
Share the exact lemwarm pause message, the full bounce message, your email provider, and your sending domain.
Include current MX, SPF, DKIM, DMARC, and CTD results, plus the time the pause happened.