---
title: "Warmup Troubleshooting"
url: https://docs.mailbeast.ai/en/articles/39-warmup-troubleshooting
collection: "Email Warmup"
updated: 2026-11-04
language: en
---

# Warmup Troubleshooting

If the **Warmup** column shows `Paused` (red triangle), warmup is on hold. This article covers everything that can put it there - and how to get it running again.

There are two ways warmup stops:

-   **Auto-paused by MailBeast** when the account hits an infrastructure issue (DNS, auth, bounces, provider policy). The badge flips to `Paused` and a hover-tooltip explains why. In the account's **Warmup** tab the switch reads **Warmup on Hold**, and there's a **Resume Warmup** button to clear it once the underlying issue is fixed.
    
-   **Turned off by you** with the **Warmup Enabled** switch in the Warmup tab. The column then shows `No`, not `Paused`. Re-enabling is just switching it back on - but see [Manually pausing warmup](#manually-pausing-warmup) for when that restarts the ramp at Day 1.
    

* * *

## When MailBeast auto-pauses warmup

Hover the `Paused` badge to see the reason. Below are all the messages you might encounter and what each one needs from you:

<table style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1" style="vertical-align: middle;"><p>Message</p></th><th colspan="1" rowspan="1" style="vertical-align: middle;"><p>What it means</p></th><th colspan="1" rowspan="1" style="vertical-align: middle;"><p>What to do</p></th></tr><tr><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>"DNS records missing. Add MX &amp; SPF records, then click Resume."</p></td><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>DNS Health Score dropped below the threshold (60). Sending with broken DNS actively hurts reputation, so warmup stops to protect the account.</p></td><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>Open the account, scroll to <strong>Health Card</strong> -&gt; DNS section, identify the failing record, fix it at your DNS provider. See <a target="_self" rel="noopener noreferrer nofollow" class="linktype-link link" data-linktype="link" href="https://docs.mailbeast.ai/en/articles/28.md">How to Set Up SPF, DKIM, and DMARC</a>. Warmup resumes on its own once the score is back at 60+, or click <strong>Resume Warmup</strong> after the fix.</p></td></tr><tr><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>"Authorization lost. Click Reconnect to restore access."</p></td><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>Google or Microsoft revoked MailBeast's access to this mailbox.</p></td><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>Click <strong>Reconnect</strong> on the account row and sign in again with your Google/Microsoft account. Warmup resumes once the account is back to Active.</p></td></tr><tr><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>"Authorization lost. Click Edit Credentials to update your password."</p></td><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>Custom SMTP/IMAP password is no longer accepted by the provider.</p></td><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>Click <strong>Edit Credentials</strong> on the account, paste the new password, run the connection test. Warmup resumes once it passes.</p></td></tr><tr><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>"Your email provider rejected outgoing messages due to a policy violation. This is a provider-level restriction and affects all sending, including warmup and campaigns."</p></td><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>The mailbox provider (Google/Microsoft/etc.) flagged the account at their side - usually for spam-related reasons. <strong>All sending is blocked</strong>, not just warmup.</p></td><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>Resolve directly with the provider (their support / abuse team). For cold email, repeat policy blocks usually mean it's time to retire the mailbox and rotate to a fresh one.</p></td></tr><tr><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>"Bounce issues detected. Check account settings, then click Resume."</p></td><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>The account hit a hard-bounce pattern that suggests an underlying problem with the mailbox itself or the lists you're sending to.</p></td><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>Audit recent campaigns for list-quality issues. Verify the account is still healthy at the provider. Click <strong>Resume Warmup</strong> once you've addressed the root cause.</p></td></tr><tr><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>"Connection issue. Verify credentials, then click Resume."</p></td><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>Generic SMTP/IMAP connection failure, not specifically auth.</p></td><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>Verify host/port/credentials, run the connection test, then click <strong>Resume Warmup</strong>.</p></td></tr><tr><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>"Domain has NULL MX (RFC 7505) – email is rejected by the receiving server. Update your DNS to resume warmup."</p></td><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>Your domain publishes a "null MX" record, which tells every server that the domain accepts no email. Warmup replies can't reach the mailbox.</p></td><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>Replace the null MX with your email provider's real MX records. Warmup resumes once DNS is fixed.</p></td></tr><tr><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>"Incoming email for this domain no longer reaches this mailbox – it now goes to a different email provider. Reconnect the mailbox or update its credentials so we can re-check where its mail is delivered."</p></td><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>The domain's MX records now point to a different email provider than the one this mailbox is connected through, so incoming mail no longer arrives here.</p></td><td colspan="1" rowspan="1" style="vertical-align: middle;"><p>If you moved the domain to a new provider, reconnect the mailbox on that provider (or update its credentials). If the MX change was a mistake, restore the previous MX records.</p></td></tr></tbody></table>

* * *

## What does NOT pause warmup

Two situations that LOOK alarming but don't pause warmup, because pausing would only make them worse:

-   **Low inbox rate during warmup.** Same logic. Warmup pulls inbox rate up over time.
    
-   **Blacklisting.** Warmup keeps running but with a downgraded pool so it doesn't impact others. See [Blacklist Monitoring](https://docs.mailbeast.ai/en/articles/32.md).
    

* * *

## Manually pausing warmup

[**Email Accounts**](https://app.mailbeast.ai/email-accounts) -> click account -> **Warmup tab** -> turn the **Warmup Enabled** switch off. Stops immediately - no more sends are planned for this account, and the column shows `No`.

> **Info:** **Turning it back on:** if the account had not finished its 14-day ramp yet and sent no warmup emails for 3 or more days, switching warmup back on restarts the ramp at `Day 1`. Accounts that had already reached `Active` continue as `Active`.

When this is genuinely useful:

-   **Decommissioning the account** for good.
    
-   **Account-level diagnostics** where you want warmup activity out of the picture so you can isolate what's affecting deliverability.
    
-   **Provider migration** that requires reconfiguration time.
    

When it's a mistake:

-   "I want my full daily limit for campaigns" - warmup already steps back automatically when campaigns are heavy. Don't disable; let it adapt. See [Warmup and Campaign Sending Together](https://docs.mailbeast.ai/en/articles/37.md).
    
-   "Warmup emails are landing in spam" - that's exactly what warmup fixes through warmup engagement. Disabling stops the fix.
    
-   "I want to change a setting" - settings update live without pausing. Just edit them.
    

* * *

## Next Steps

-   [What to Expect from Warmup](https://docs.mailbeast.ai/en/articles/36.md) - what each badge means in normal operation.
    
-   [Configuring Your Warmup](https://docs.mailbeast.ai/en/articles/35.md) - settings panel and what each control does.
    
-   [Blacklist Monitoring](https://docs.mailbeast.ai/en/articles/32.md) - separate health signal that doesn't trigger Resume but still needs attention.
