Why reconnecting doesn't fix this mailbox

Because the sign-in was never the problem. When a mailbox keeps asking to be reconnected within minutes of you reconnecting it, what has almost always happened is that your email provider has switched off incoming access for that one mailbox — the permission that lets an outside app read the mail arriving in it. WarmySender can still send from that mailbox perfectly well. What it cannot do is read what arrives. Reconnecting, or creating a fresh App Password, re-supplies a sign-in that was already correct, so the mailbox connects, is refused when it tries to read, and reports the same thing again. The change that fixes it is a setting on the email account itself, and it is made by whoever administers that account.

WarmySender runs your outreach on autopilot with AI agents across Cold Email, Email Warmup, LinkedIn, Instagram and Multichannel sequences — plus real-time email verification. This guide answers a mailbox-connection question.

What you will see

The pattern is distinctive, and it is worth checking against what you are seeing before you follow the rest of this page:

• The mailbox shows that it needs reconnecting, or shows a connection warning.
• You reconnect it. It accepts your details and goes green.
• Within minutes — sometimes before you have finished the next task — it is back in the same state.
• Meanwhile the mailbox is still sending. Campaign emails go out. Warmup mail goes out. Your daily send counts keep moving.

That last point is the giveaway. A mailbox with a genuinely wrong password cannot send either. If sending works and only the connection warning persists, the two halves are being treated differently by your provider — which is exactly what this state is.

What it actually means

Every mailbox has two separate permissions, and they are controlled independently:

• Permission to send — lets WarmySender deliver mail out of the mailbox.
• Permission to read incoming mail — lets WarmySender look at mail arriving in the mailbox.

Your provider has turned the second one off for this mailbox. When WarmySender signs in to read, the provider answers, in effect, "signing in to read is switched off here." It is not saying the password is wrong. It is not saying the account is locked. It is declining the whole activity, and it would decline it for any correct password in the world.

This is usually deliberate, and usually not aimed at you. It is a common default on business email plans, and it is often applied account-wide by an administrator as a security measure — sometimes years ago, sometimes by a policy that was switched on for everyone last week.

Why reconnecting cannot fix it

Reconnecting does exactly one thing: it gives WarmySender a fresh, valid way to sign in to the mailbox. That is genuinely the right fix when a sign-in has lapsed or a password has changed.

Here, the sign-in details are already accepted. The refusal happens after a successful sign-in, at the moment reading is attempted. So a new App Password, a new sign-in, or removing and re-adding the mailbox all hand over a better version of the one thing that was never wrong. The mailbox will connect, try to read, be declined, and report the same state again — which is why it comes back so quickly.

You do not need to keep trying. Nothing you can do from your side of the connection changes the answer.

An example

Priya runs outreach for a 40-person company and connects [email protected] to WarmySender. It connects, and her campaign starts sending that afternoon — 60 emails out on day one, replies landing in her mailbox as normal.

The next morning the mailbox is asking to be reconnected. She generates a new App Password and reconnects. Green again. By lunchtime it is asking again. She does it twice more over the next two days, assuming she has copied something wrong.

Nothing was wrong with her password. Her company's IT provider had incoming access switched off across the whole company as a standard security setting. Priya's campaigns had been sending the entire time and never stopped — the only thing that was not working was WarmySender reading her incoming mail, which is what warmup measurement and reply detection depend on.

She forwarded one sentence to her IT contact. He changed the setting for her mailbox in a couple of minutes, and the warning cleared on its own without her reconnecting again.

The one thing to ask for

Send this to whoever administers your company email — your IT person, your email provider's support, or whoever set up your account. If you administer it yourself, this is the setting to change on your own account.

"Please turn incoming mail access back on for the mailbox [your address], so an approved outside application can read mail arriving in it. It is currently switched off for this mailbox. Sending is unaffected and already works."

A few notes that save a round trip:

• It is usually a per-mailbox setting, so it can be enabled for your address alone without changing anything company-wide.
• On Microsoft 365 it sits with the mailbox's email app settings, in the admin area rather than in your own mail settings.
• On Google Workspace it sits with the user's email settings in the admin console, and may also need to be enabled on the account itself.
• Ask them to confirm when it is done. The change takes effect quickly, but not always instantly.

What still works while this is happening

This is worth knowing before you pause anything:

• Sending continues. Campaigns keep sending on schedule, at the same limits, from this mailbox.
• Your mail is untouched. Nothing is lost, delayed or changed in your mailbox. Mail arrives normally and you can read it yourself as usual.
• Warmup measurement pauses. Confirming where warmup mail landed requires reading the inbox, so placement figures for this mailbox stop updating.
• Reply detection pauses. Sequence steps that stop automatically when someone replies rely on watching the inbox, so they cannot see replies to this mailbox until access is restored.

Because of the last two, it is worth getting fixed rather than living with — but there is no emergency, and no reason to delete and re-add the mailbox.

How you will know it is fixed

You do not need to reconnect after the setting changes. WarmySender keeps checking the mailbox on its own, and the first successful read clears the warning automatically — usually within a few minutes of the change taking effect.

Placement figures for the mailbox start moving again on the next warmup cycle. If you want to confirm, your warmup inbox rate is the number that resumes updating once reading works again.

If the warning is still there several hours after your administrator confirms the change, contact us and we will look at what the provider is answering for that mailbox.

Common questions

I reconnected the mailbox and it asked to be reconnected again. What is wrong?

Almost certainly nothing about your password. When a mailbox returns to the reconnect state within minutes, your email provider has switched off incoming access for that mailbox — the permission that lets an outside app read mail arriving in it. Your sign-in is accepted; the refusal happens afterwards, when reading is attempted. That is why supplying a better sign-in does not change the outcome.

Will a new App Password fix it?

No. A new App Password is the right fix when a sign-in has lapsed or a password has changed, but here the sign-in details are already being accepted. The provider is declining the reading activity itself, and it would decline it for any correct password. Someone who administers the email account has to turn incoming access back on.

Are my campaigns still sending?

Yes. Sending and reading incoming mail are two separate permissions on the same mailbox, and only the reading one is switched off. Campaigns keep sending on schedule at the same limits, and warmup mail keeps going out. If sending had genuinely broken, the mailbox would not be sending at all — so a mailbox that is sending while showing a connection warning is the signature of this state.

What exactly should I ask my IT administrator to do?

Ask them to turn incoming mail access back on for your specific mailbox, so an approved outside application can read mail arriving in it, and mention that sending is unaffected and already works. It is usually a per-mailbox setting, so it can be enabled for your address alone without changing anything company-wide. On Microsoft 365 it sits with the mailbox email app settings in the admin area; on Google Workspace it sits with the user email settings in the admin console.

Why is this switched off if I never turned it off?

It is a common default on business email plans, and it is often applied across a whole company by an administrator as a security measure. It may have been set years ago or switched on for everyone recently. In most cases it was not aimed at your mailbox specifically, and it can be enabled for your address without weakening the setting for everyone else.

What stops working while incoming access is off?

Two things, both of which need to read the inbox. Warmup placement figures for that mailbox stop updating, because confirming where warmup mail landed means looking in the inbox. And sequence steps that stop automatically when someone replies cannot see replies to that mailbox. Your own mail is untouched — nothing is lost or delayed, and you can read it yourself as normal.

Do I need to reconnect once it is fixed?

No. WarmySender keeps checking the mailbox on its own, and the first successful read clears the warning automatically, usually within a few minutes of the change taking effect. Placement figures start moving again on the next warmup cycle. If the warning is still showing several hours after your administrator confirms the change, contact us and we will look at what the provider is answering for that mailbox.