Archiving Emails from Zimbra

Revision as of 04:41, 20 June 2010 by Vivian (talk | contribs)

Please note: This tutorial only covers the specifics of archiving a Zimbra server. It is assumed that you already have a MailStore Server installation or test installation and are familiar with the fundamentals of MailStore Server. Please refer to the Manual or Quick-Start-Guide.

MailStore Server offers several ways to archive emails from a Zimbra server, which are described below. If you are not sure which archiving method best suits your company, please refer to chapter Choosing the right archiving strategy.

Archiving Individual Mailboxes

If you have not yet allowed IMAP access to the mailboxes of the Zimbra server, please follow the instructions under step 1. Otherwise, proceed to step 2.

Step 1: Enabling IMAP Access

To allow access to the mailboxes of the Zimbra server via IMAP, the service class has to be customized accordingly.

Please note:When using a Hosted Zimbra Server, please contact your Zimbra Hosting Provider for setting up IMAP access.

  • Open any web browser and navigate to the web-based Zimbra administration console of your Zimbra server. The standard address is https://zimbrahostname.domain.tld:7071.
  • Log in to the Zimbra administration console.
  • Click on Configuration and then on Service Class. Select the appropriate service class, e.g. default to change the default settings for all users.
  • Click on the Functions tab.
  • Under Mail Functions, enable the checkbox IMAP Access.

Step 2: Configuration of MailStore Server

When archiving individual mailboxes, a Zimbra server functions the same as any other email server. Please refer to the corresponding chapter Archiving Server Mailboxes in the MailStore Server manual.

Archiving Multiple Mailboxes in One Step

Archiving Incoming and Outgoing Emails Directly

Zimbra Collaboration Suite uses the mail transfer agent Postfix for sending and receiving emails. The recommended way to integrate MailStore into a Zimbra Collaboration Suite environment therefor is the same as described in our Postfix article.