zintara.io

Mailbox troubleshooting · Practical guide

Connect a custom SMTP and IMAP mailbox: prepare the full configuration

Prepare sending and incoming settings together. A custom mailbox is ready for campaign use only after both transport paths and the intended sender identity have been checked.

Reviewed · Examples are illustrative

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

Define the decision

Do not infer mail settings from the website host or another employee's client. Obtain the provider's current configuration for this account. Keep the authorized identity, outgoing endpoint and incoming endpoint in one review record so a partial connection is not mistaken for a complete setup.

Work through the procedure

  1. Collect SMTP host, port and encryption mode plus IMAP host, port and secure-access requirements from the provider.
  2. Confirm the authentication method permitted for this mailbox and who owns its credentials or authorization grant.
  3. Enter settings through the supported connection form and run both connection tests.
  4. Send to an owned address, reply from that address and verify the incoming message. Review display name and signature before selecting the account for a campaign.

Worked example

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

Connection worksheet
Mailbox identity: confirmed owner
SMTP: provider-documented host, port, mode
IMAP: provider-documented secure incoming endpoint
Credentials: authorized, stored through application controls
Evidence: sending test + incoming test + controlled reply

Read the result

The controlled reply completes a loop that separate green connection tests may not fully demonstrate. If the reply exists in provider webmail but not the application, investigate incoming sync and folder placement. If sending fails, identify the transport or authorization stage before changing unrelated incoming settings.

Check before moving on

  1. Avoid posting credentials in support messages.
  2. Confirm the account selected by the campaign is the tested account.
  3. Check remaining campaign eligibility and schedule separately from mailbox setup.

Limits and next action

This guide does not claim that every provider or authentication scheme is supported. Zintara's custom connection path has specific secure transport requirements and reads INBOX for sync. Verify compatibility before relying on a shared mailbox, alias or unusual provider configuration.

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