zintara.io

Mailbox troubleshooting · Practical guide

Replace mailbox credentials without losing the recovery trail

Update credentials through the supported connection path, then verify sending and incoming access. Preserve the incident context so a successful login is not mistaken for complete campaign recovery.

Reviewed · Examples are illustrative

Who this helps: Mailbox owners and service operators diagnosing outreach connections.

Define the decision

Credential changes can follow routine rotation, account policy changes or a revoked grant. Record why the update is needed and which services share the credential. Avoid distributing the new secret through chat or copying it into a broad-access incident note.

Work through the procedure

  1. Confirm the authorized mailbox owner and the provider-supported authentication method.
  2. Record affected campaigns and the last known successful send and sync, without storing secret values in the worksheet.
  3. Update the credential through the application controls and run scoped outgoing and incoming tests.
  4. Review replies and uncertain attempts from the interruption before resuming pending sequence work.

Worked example

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

Rotation worksheet
Reason: authorized credential replacement
Owner: mailbox administrator
Affected paths: SMTP and IMAP
Validation: both tests pass; controlled reply visible
Remaining review: messages and responses during the outage

Read the result

The validation proves the new connection works for the tested paths. It does not establish that every earlier message failed or that all pending follow-ups remain appropriate. Separating connection repair from conversation review prevents a routine rotation from producing accidental duplicate or stale outreach.

Check before moving on

  1. Confirm no old credential remains in an unintended application connection.
  2. Verify the campaign still selects the correct mailbox.
  3. Follow the provider's authorized process for retiring the superseded credential or grant.

Limits and next action

This guide does not prescribe a provider-specific rotation policy or ask you to weaken account security. Zintara supports particular connection methods; use the one your mailbox policy permits. Do not replay uncertain sends merely because the replacement credential now authenticates.

Source: Zintara unified inbox product context

Source references

Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features. Check current provider guidance before changing mailbox configuration.

Related guides

Explore the Zintara workflow