Kerio Connect - Cloud Archive problem [message #145592] |
Thu, 18 April 2019 21:23  |
bruggles
Messages: 150 Registered: April 2008
|
|
|
|
We have our Kerio Connect to Archive email to Barracuda Cloud Archive, I just noted that when we have users message options set to This user can send/receive messages to/from his/her own domain only. The emails do not go out to the Cloud. Can someone tell me how to fix this or if Kerio could Fix this in the next release as I think this is a very important issue as archiving of emails is very important to us.
Thank You
[Updated on: Thu, 18 April 2019 21:24] Report message to a moderator
|
|
|
|
|
|
Re: Kerio Connect - Cloud Archive problem [message #145684 is a reply to message #145592] |
Tue, 30 April 2019 18:07  |
Bud Durland
Messages: 586 Registered: December 2013 Location: Plattsburgh, NY
|
|
|
|
bruggles wrote on Thu, 18 April 2019 15:23I just noted that when we have users message options set to This user can send/receive messages to/from his/her own domain only. The emails do not go out to the Cloud.
I'm presuming you set up Kerio connect to forward every message to an 'archive' address ('Config' / 'Archving and backup' / 'archive to remote email address') and entered an e-mail address. Generally speaking, messages get delivered to the mail archiver one of two ways:
- Direct: The e-mail you entered is the unique Barracuda archive address for your organization (for example, 'MyArchive<_at_>cloud.barracuda.com). Archiving mail is basically now a universal forwarder. All messages are sent via normal SMTP to that address, as if the users themselves sent an e-mail to it. This will fail for users that have been flagged as 'send/receive from their domain only', because the destination is a different domain
- Pull: The e-mail you entered is for a special 'archive' account on your kerio mail server. You then configure the cloud server to periodically log in to that account to download and delete the archived messages. This will work regardless of a person's 'their domain only' setting, because the server doesn't have to relay it; it effectively just makes a copy in that archiving account.
Hope this helps
|
|
|