ELOxc supports several methods to set permissions for stored messages. Keep in mind that mailbox owners do not always have an ELO user account. It is therefore recommended that you create a main folder with exclusive access for the mailbox owner before processing a mailbox for the first time so that the stored message contents are not compromised. The default configuration in ELOxc uses the forms "Folder" and "E-mail" whose permission settings are already configured for this case and automatically take on the permissions of the main folder.

When importing users from the external directory using ELOxc, you must ensure that no conflicts with existing user data occur. ELOxc identifies existing users with the properties "objectGuid", "SAMAccountName", "UserPrincipalName", and "mail". If there is no match based on these attributes, the mailbox owners are created as new ELO users.

If the storage paths are configured accordingly, mailbox owners who are identified as ELO users can have personal folders in the repository that only they have access to, which ensures that message contents are not compromised on initial storage.

You can only use LDAP import and user import with ELOxc simultaneously if the LDAP import is configured to use SAMAccountName as "Name", UserPrincipalName" as "Windows user", and mail as "E-Mail". You also have to apply "objectGUID" from the directory as the GUID of the new ELO user. The GUID must have the format (00000000-0000-0000-0000-000000000000) (round brackets). If this is not possible, you should only import users with one of the two components.