Download Zarafa Collaboration Platform - The Administrator - NIT

Chapter 5. Configure 3rd Party Components
virtual_mailbox_maps = hash:/etc/postfix/virtual
virtual_alias_maps = hash:/etc/postfix/virtual
virtual_transport = lmtp:localhost:2003
The file /etc/postfix/virtual should contain all email addresses and aliases of a user, in the
following structure:
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected], [email protected]
The left column contains the email address or alias, the right column contains the primary email
addresses on which the message should be delivered.
After all users and aliases are added to this file, a hash map needs to be created. The following
command will create the actual hash map /etc/postfix/virtual.db.
postmap /etc/postfix/virtual
All incoming emails are delivered to the zarafa-dagent over LMTP using the primary mail address
of as specified in the hash map.
After changing the configuration files restart Postfix by its init script:
/etc/init.d/postfix restart
Make sure the zarafa-dagent runs as daemon and is started at boot time:
chkconfig zarafa-dagent on
/etc/init.d/zarafa-dagent start
Note
It’s advised to enable logging of the zarafa-dagent when running in LMTP mode
for monitoring purposes. To alter logging options for the zarafa-dagent, adjust the
configuration file: /etc/zarafa/dagent.cfg.
5.5. Configure Z-Push (Remote ActiveSync for Mobile
Devices)
This chapter describes how to configure the Z-Push software to bridge ZCP with ActiveSync enabled
PDAs and smartphones.
Z-Push is available as an open source project on Sourceforge - http://z-push.sourceforge.net
In this manual only the server part of Z-Push is discussed, please refer to our User Manual for
instruction on configuring mobile devices.
Mobile phones, smartphones and PDAs can be synchronized because Z-Push emulates the
ActiveSync functionality of a MS Exchange server on the server side, allowing mobiles to synchronize
54