Sent folder sync troubleshooting: separate provider copies from application records

Define the decision

The reviewed inbox synchronizer reads INBOX rather than importing the provider’s full Sent folder. Zintara’s own outgoing records and messages sent in another client therefore have different paths into the application.

Work through the procedure

1. Identify which client originally sent the message.
2. Confirm whether it was a Zintara campaign or inbox action.
3. Locate the provider copy and retain its Message-ID.
4. For a missing application record, investigate the original action and result; for external sent mail, recognize the current import boundary.

Worked example

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

Message sent manually from Outlook webmail
Provider Sent: contains a copy
Zintara INBOX sync: does not import that folder
Conclusion: absence is not by itself an IMAP login failure

Read the result

A provider can also store a sent copy according to its own behavior. The existence of that copy does not prove the application has recorded a campaign event or matched a lead.

Check before moving on

1. Check the actual sending client and account.
2. Use a controlled Zintara send to test the application path.

Limits and next action

Do not claim full historical mailbox synchronization. If full Sent import is required, record it as a capability requirement rather than a hidden setting to enable.

Source: Zintara inbox synchronization context