Warming
Warmup bounce and disabled warmup
If a warmup message bounces, EmailPal can disable warming on that mailbox so we stop hitting a broken address. Fix authentication, credentials or the mailbox itself, then resume.
Why warming disables itself
Warming is supposed to look like a healthy conversation. A bounce says the opposite: the mailbox, the domain or the route is rejecting mail. Continuing the ramp on a bouncing address trains a bad signal and wastes seed capacity.
When we see a warmup bounce, warming on that mailbox can go on hold. Campaign sending should stop too until you know why.
Typical causes
- MX missing or pointing at the wrong host
- Mailbox deleted, full, or never created
- SMTP authentication failed after a password rotation
- Connected Gmail/Outlook token expired
- Provider rejected the message (policy, blocklist, or invalid recipient on the seed side)
What to do
- Confirm the mailbox still exists and IMAP/SMTP work. SMTP and IMAP credentials.
- Re-verify DNS. DNS verification failed.
- If this is a connected Google or Microsoft mailbox, reconnect it. Warm Gmail, Outlook or your own server.
- Resume warming from the mailbox row. Enable, pause or resume warming.
- If it bounces again immediately, replace the mailbox. Do not keep enabling.
FAQs
Will EmailPal resume warming automatically?
Not after a bounce hold. You resume once the cause is gone, so we do not silently retry a dead mailbox.
Does this happen on pre-warmed leases?
Rarely — those addresses already finished a ramp. If a leased inbox bounces in warming after you claim it, treat it as urgent and open a ticket.