Disconnect a mailbox safely: account for pending sends and replies

Define the decision

A mailbox can be selected by several campaigns and still receive replies to older messages. Removing access can therefore stop more than new sending. Plan who will watch outstanding conversations and whether another authorized person should take over before the original connection is retired.

Work through the procedure

1. List campaigns using the account and pause or review their pending work through supported controls.
2. Investigate uncertain attempts before removing evidence needed for reconciliation.
3. Assign coverage for replies to previously sent messages, using provider access or an approved handoff.
4. Disconnect through the available product controls and verify affected campaigns no longer rely on the retired connection.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Retirement record
Mailbox owner leaving the team
Two campaigns select the account
One unresolved send attempt remains
Action order: contain pending work, reconcile attempt, assign reply coverage, retire access
Do not delete conversation evidence to make the account disappear.

Read the result

The unresolved attempt belongs before retirement because removing access may make provider evidence harder to retrieve. Reply coverage also remains relevant after sending stops. A recipient replying to yesterday's email does not know that an internal account transition occurred.

Check before moving on

1. Confirm ownership and authorization for any replacement sender.
2. Review signatures and old links in copied campaign text.
3. Record the retirement date and the person responsible for outstanding conversations.

Limits and next action

This is a transition checklist, not a promise that disconnecting automatically transfers history, revokes every provider token or reassigns campaigns. Verify the behavior of the controls available in your Zintara deployment and handle provider-side access changes with the authorized mailbox owner.

Source: Zintara unified inbox product context