It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Campus Barracuda Campus

Zimbra Mail Server Deployment

  • Last updated on

This article refers to the Barracuda Message Archiver version 5.0 and higher, and the Zimbra® Mail Server.

Use the following steps to configure Zimbra Mail Server for journaling to the Barracuda Message Archiver:

Step 1. Configure Zimbra

Use the following steps to configure Zimbra Mail Server for Journaling.

  1. On the system running Zimbra, add the following line to the /etc/hosts file, replacing 127.0.0.1 with the IP address of your barracuda Message Archiver:
    127.0.0.1 barracuda.company.com
  2. On the Zimbra Server, telnet to barracuda.company.com on port 25 to verify there is a clear line of connectivity between the two systems.
  3. On the Zimbra Server, type the following command, replacing company.com with the domain name of your company:
    zmarchiveconfig enable <journal@company.com> archive-address archive@barracuda.company.com archive-create false

Step 2. Set up the Port Zimbra is bound to for Milters

Zimbra v5 RC2 embeds a new version of postfix.

  1. Execute the following command as the Zimbra user to verify and change the port that Zimbra is bound to for milters:
    zimbra@server:~$ zmprov gs server.example.com zimbraMilterBindPort                     #### (Shows the current port)
    zimbra@server:~$ zmprov ms server.example.com zimbraMilterBindAddress 192.168.0.22    #### (replace 192.168.0.22 with ip address of Archiver server)
    zimbra@server:~$ zmprov ms server.example.com zimbraMilterBindPort 8092                 #### (Set the port to 8092)
    zimbra@server:~$ zmmtactl restart                                                       #### (Reread the configuration)
  2. Log in to the Zimbra Admin Console.
  3. Go to Server Settings > MTA.
  4. Turn on Enable milter server, and enter the IP address of the mail server in the associated field.

  5. Click Save.

    There are reports that Zimbra overwrites the main.cf configuration upon service restart. To avoid this, mark /opt/zimbra/postfix/conf/main.cf as read-only. Note however, setting to read-only prevents any further changes. If you encounter problems when reverting the main.cf file or are unable to change anything, contact Barracuda Networks Technical Support.

If step 2 is successful, your deployment is complete. However, is step 2 is unsuccessful, you may have a version of Zimbra that does not embed a version of postfix that includes support for sendmail milters. In that case, complete the following steps:

  1. Add the following to the main.cf file: 
    #vim /opt/zimbra/postfix/conf/main.cf ... ... sender_bcc_maps = hash:/opt/zimbra/postfix/conf/sender_bcc

  2. Add the following to the /opt/zimbra/postfix/conf/sender_bcc file:
    #vim /opt/zimbra/postfix/conf/sender_bcc @company.com archive@barracuda.company.com

    Mail sent by all users of the company.com domain are now copied to the archive@barracuda.company.com  mail account.

  3. From Zimbra MTA, run telenet barracuda.company.com 25; 220 EHLO should display.
  4. Use the following command to restart Zimbra:

    #cd /opt/zimbra/postfix-2.2.9
    #postmap sender_bcc
    #service zimbra restart

  5. You may need to update your hosts file to point barracuda.company.com to your Barracuda Message Archiver IP address.