Disconnected Mailbox OAuth: Preflight Checks Before a Campaign Runs
A practical, provider-aware guide to mailbox OAuth disconnected, with a decision table, workflow, and evidence-based caveats.
Product & Engineering · September 25, 2026 · 2 min read
Mailbox oauth disconnected starts with a scoped decision: diagnosing a disconnected mailbox OAuth connection before a campaign can enqueue or send. There is no provider-neutral shortcut or universal safe number. Build a small, observable plan, record the evidence it produces, and make the pause and recovery path explicit before adding volume or complexity.
For context, start with the deliverability map, then review why a new domain needs a gradual warm-up, the difference between a sending domain and a mailbox, and email-sending observability before changing production routing.
Decide what the system must prove
The first question is not how fast to send. It is what this workflow must prove about diagnosing a disconnected mailbox OAuth connection before a campaign can enqueue or send. Separate authentication and account access from recipient outcomes, and separate a provider ceiling from an internal operating limit. The table below turns that distinction into fields an operator can review.
| Check | Question | Evidence |
|---|---|---|
| Connection | Is the token present and accepted? | Provider response and timestamp |
| Consent | Was access revoked or scope changed? | Admin/user audit record |
| Workflow | Is the mailbox still eligible? | Campaign assignment and pause state |
| Test | Can send, receive, and reply work? | Controlled test message and reply |
Practical workflow
- Stop new assignment and capture the mailbox, provider, account, campaign, and last successful event..
- Check token status, consent, scopes, account access, and any provider or admin change..
- Reconnect only through the approved flow.
- Run a controlled send, receive, reply, and bounce-path test, then re-enable campaign work deliberately..
The useful output is a decision record: what was observed, what changed, who owns the next action, and what would cause a pause or rollback. A provider document can define a limit or behavior, but it cannot tell you that your audience, content, or mailbox mix is safe for a particular campaign.
Edge cases and limits
A reconnect can restore access without restoring correct ownership, suppression, or reply routing. Treat access recovery and workflow readiness as separate checks. Preserve provider responses and timestamps, and label unmeasured assumptions as assumptions. If the issue spans multiple providers, compare their native evidence before normalizing it into one report.
Where RepMail fits
RepMail can be used as the operational layer for the workflow: keep mailbox and campaign identifiers attached to events, use suppression and reply ownership as explicit controls, and review outcomes by provider rather than relying on a single aggregate. It does not turn a provider limit or a warm-up signal into a delivery guarantee.
References
Resources in this guide
| Check | Question | Evidence |
|---|---|---|
| Connection | Is the token present and accepted? | Provider response and timestamp |
| Consent | Was access revoked or scope changed? | Admin/user audit record |
| Workflow | Is the mailbox still eligible? | Campaign assignment and pause state |
| Test | Can send, receive, and reply work? | Controlled test message and reply |
- Stop new assignment and capture the mailbox, provider, account, campaign, and last successful event.
- Check token status, consent, scopes, account access, and any provider or admin change.
- Reconnect only through the approved flow; verify that the requested scope matches the documented workflow.
- Run a controlled send, receive, reply, and bounce-path test, then re-enable campaign work deliberately.
Frequently asked questions
What causes OAuth disconnection?
Possible causes include revoked consent, expired or invalid tokens, account changes, scope changes, or provider/admin policy changes. Inspect evidence rather than guessing.
Should I keep retrying while disconnected?
No. Pause new work and retries until the connection state and queued messages are understood.
What is a safe reconnect test?
Use a controlled message to an approved test address, verify send and receive behavior, then check reply, bounce, logging, and suppression handling.
Continue learning
Read the complete deliverability guide
Use the hub to connect mailbox operations with authentication, reputation, placement, and list quality.