Overview

Users of Kerio Connect who relay emails from 3rd party systems via direct SMTP authentication from local accounts may encounter a challenge when trying to keep a local copy of all emails sent this way, particularly in the users' 'Sent Items' folder.

Kerio Connect does not have a built-in feature to automatically save copies of outgoing SMTP emails when they are sent via third-party applications or services using SMTP authentication. 

Solution

To keep a local copy of all emails sent via direct SMTP authentication from local users in Kerio Connect, consider the below workarounds:

• Including a BCC to the actual user: This will ensure a copy of the emails is kept in the Inbox. However, this may not be ideal as there is no way to keep copies of the emails in the Sent Items folders of the users.

• Archiving the whole server may help achieve this, however, it may pose the same issue of the emails not being easily accessible to end users, as they would need to have access to the archive folders. Whole server archiving is the only option covering all types of emails (outgoing + relayed, for example). See Archiving in Kerio Connect for additional details.
  • Note: Archiving individual domains does not archive relayed messages.

Summary

While Kerio Connect does not have a built-in feature to automatically save copies of outgoing SMTP emails, users can consider workarounds such as including a BCC to the local user or archiving the whole server. These methods, however, have their limitations and may not be ideal for all users.

FAQ

1. Can I keep a local copy of emails sent via SMTP authentication in the 'Sent Items' folder in Kerio Connect?
   No, Kerio Connect does not have a built-in feature to automatically save copies of outgoing SMTP emails in the 'Sent Items' folder when they are sent via third-party applications or services using SMTP authentication.
2. Can I archive individual domains to keep a local copy of emails sent via SMTP authentication?
   No, archiving individual domains does not archive relayed messages. You can consider archiving the whole server as a workaround.