Table of Contents
The concept of ownership
When an email enters into the archiver, the ownership of that email is assigned to one ore more email addresses. Only the users that own those email addresses can see the email
For example: the owner an email is user@example.com, which is John’s email address, so John can see this email.
The same applies to email aliases. For example sales@example.com is an email alias for both Josh and Margareth, so Josh and Margareth can see this email. The list of email aliases assigned to each user defines what email the user can see.
How ownership is assigned when email is imported into the archiver
The criteria for assigning the owners of each imported email is summarized in the table below.
For manual imports (PST or EML archives) the user can be specified on import. If not specified, the ownership is derived from the email headers.
When Journaling is enabled (either via SMTP or IMAP/POP3) the ownership is defined by the journal fields.
When emails are forwarded to the arvhiver, the ownership is defined by the email header fields.
Finally, when emails are imported through the Connector API (Exchange, Microsoft 365, Google Workspace, Zimbra, IMAP), the ownership is determined by the configured users for which the API call is made.
The following table summarizes the source of ownership information for each import method.
| PST or EML (specifying a user on import) | PST or EML (without specifying a user on import) | Journaling (Exchange format) either SMTP or IMAP/POP3 | Forwarding either SMTP or IMAP/POP3 | Connector import via API | |
| Header-From | X | X | |||
| Header-To | X | X | |||
| Header-Cc | X | X | |||
| Envelope-From | X | X | |||
| Envelope-To | X | X | |||
| Journaling-Sender | X | ||||
| Journaling-Bcc | X | ||||
| Journaling-CC | X | ||||
| Journaling-To | X | ||||
| Journaling-Recipient | X | ||||
| Specified user | X | X |
The ownership