Zarafa

Languages:

English  • français

	Skill level: advanced
	The instructions on this page may require deviations from standard procedures. A good understanding of linux and Koozali SME Server is recommended.

Maintainers

Darrell May

Stephen Noble http://dungog.net/wiki

Version

smeserver-zarafa

The latest version of smeserver-zarafa is available in the SME repository, click on the version number(s) for more information.

The contrib version is broken, use the version in smetest, --enablerepo=smetest

Description

http://www.zarafa.com

Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft Outlook, which enables the sharing of mail and appointments from Outlook and a web-based interface.

Installation

Latest zarafa tested version

Information on previous versions of zarafa rpms can be found in the changelog document [1]

Zarafa rpms installation

http://www.zarafa.com/download-community

Distribution = Rhel 4

3 Outlook license version (or just disable licensed service for the GPL version)

tar -zxvf zarafa-6.*.tar.gz
yum localinstall libvmime*.rpm libical*.rpm zarafa-6*.rpm zarafa-webaccess-6*.rpm zarafa-licensed-6*.rpm

	Note:
	From Zarafa 6.30.X you have to enable InnoDB support in MySql in order to get zarafa-server running, for information on how to do so, see MySQL#Enable_InnoDB_engine

Updating

Download newer rpms, then

rpm -Uvh zarafa-6*.rpm zarafa-webaccess-6*.rpm zarafa-licensed-6*.rpm libvmime*.rpm libical*.rpm
/etc/e-smith/events/actions/zarafa-update

smeserver-zarafa

Note:

This is a beta release. Possibly for production servers after testing with per user settings first. You select 'per user' or 'globally' where you want mail delivered via db entries. Default leaves mail going to users ~/Maildir. A minimal amount of disruption can be achieved by enabling per user, that user just enables another IMAP connection in their email client on port 8143, they could then just drag and drop mail between SME to Zarafa mail stores.

Install a fresh SME 7.4 test server and perform the following:

yum install smeserver-zarafa --enablerepo=smecontribs

After rpm install execute the following:

/etc/e-smith/events/actions/zarafa-install
signal-event post-upgrade; signal-event reboot

Note:

You will be prompted to select the user plugin you wish to test. We suggest the db method. Note the ldap plugin is currently not supported in the rpm. The unix plugin reads existing SME user details but also includes groups and machine names (messy). The db plugin is pristine however you need to enter all the user details. In both cases the user must exist in SME first as a standard user. A decision on which plugin we will choose for final deployment is still to be determined.

Usage

Managing Users

Enable mail delivery to zarafa for users:

for all users

config setprop zarafa-server GlobalForward enabled

or for individual users

db accounts setprop $USERNAME zarafa enabled

apply

/etc/e-smith/events/actions/qmail-update-user

If you chose the db plugin, run:

/etc/e-smith/events/actions/zarafa-create-user

or manage zarafa users with the panel ( smeserver-zarafa >= 0.29 )

Webmail

Access with a browser,

https://server/zarafa
https://server/webaccess
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')

Outlook

To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz

• Outlook 2007 client generates Error 0x80070057 on send and receive if the Zarafa

server is added to an existing profile. Creating a new clean profile solved the problem.

IMAP

The default ports for Zarafa are 8000 + default values

so imap = 8143, imaps 8993

SME and Zarafa use different folder naming.

drafts > Drafts          [client specific ?, Drafts is default Thunderbird-2.0]
sent-mail > Sent Items
trash > Deleted Items
junkmail > Junk E-mail

Thunderbird

The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder,

Change in the config editor

Preferences > advance > config editor, find mail.server.number and add new string as below

user_pref("mail.server.server5.port", "8143");
user_pref("mail.server.server5.name", "zac@232.net");
user_pref("mail.server.server5.numHdrsToKeep", 30);
user_pref("mail.server.server5.timeout", 29);

right click > new
preference name > mail.server.server5.trash_folder_name
value > Deleted Items

+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");

Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders

If junkmail exists just delete it.

Calendar CalDAV / iCal

Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...

	Note:
	Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: /etc/init.d/zarafa-ical restart

• In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below
• In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)
• In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below

URL	Calendar
http://server:8089/ical/	user's own default calendar via ical (not recommended)
http://server:8089/caldav/	user's own default calendar
http://server:8089/caldav/<other-user>	0ther-user's calendar
http://server:8089/caldav/<user>/<calendar>	user's self created calendar in user's (own) store
http://server:8089/caldav/<user>/<calendar>/<subcal>	user's self created subcalendar in a self created calendar
http://server:8089/caldav/public/<calendar>/	calendar folder in the public folder
URL For MAC OSX ical client
http://server:8089/caldav/	User's calendar list
http://server:8089/caldav/<other-user>	Other-users calendar list
http://server:8089/caldav/public	Public folders list

Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.

Mobile synchronisation

To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.

You can find the original Z-push installation documentation here: http://download.zarafa.com/zarafa/release/docs/z-push_installation_manual.en.pdf

Download the latest Z-push version (see: http://z-push.sourceforge.net).

wget http://download2.berlios.de/z-push/z-push-1.2.2.tar.gz

Extract the files:

tar -zxvf z-push-1.2.2.tar.gz -C /var/www/html

'State'-dir needs to be writable for apache:

chmod 755 /var/www/html/z-push/state
chown www:www /var/www/html/z-push/state

Expand and restart

expand-template /etc/httpd/conf/httpd.conf
sv restart httpd-e-smith

SSL Synchronization with Windows Mobile devices

Synchronisation over a secured connection is possible if you can add your site as a trusted one with corresponding certificate on your mobile.

This is the case for Windows mobile 6 (WM6) devices. Problems should occurs on several WM5 devices, because of a bug that limits addition of certificates with that OS.

Here are the steps to add your server as a trusted platform on your WM6 mobile :

1. to convert your server's certificate into a (Binary coded DER X.509) .cer file you can either run the following command and skip to step 4 or just start at the next step.

 openssl x509 -in /home/e-smith/ssl.pem/<certificate name>.pem -inform PEM -out /root/<certificate name>.cer -outform DER

2. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer

3. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :

• in microsoft windows open a certificate by double clicking on it
• in "Detail" Tab pane choose "Copy to file"
• Choose Binary coded DER X.509 (.cer) format
• save resulting .cer certificates on local machine

4. transfer .cer certificates on your mobile using windows explorer

5. When done, on your WM6 mobile use file explorer to open those certificates. When opening one, the certificate is automatically added to trusted sites.

6. You can then change your Exchange server parameters to use SSL. It will be asked to reenter your password.

Know working hardware

Tested and working with WinMobile 6.1 on a HTC TyTN II over a SSL connection / mail-push is working.

Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.

Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.

Tested and working with IPHONE. Push mail not tested.

Tested and working with Nokia 6120 Classic. Push mail not tested.

Extras

Command line admin

man zarafa for details

List users:

/usr/bin/zarafa-admin -l

Update a user to admin status:

/usr/bin/zarafa-admin -u <username> -a 1

Migrating users and data to Zarafa

http://wiki.contribs.org/Imapsync

Customizing the Calendar

The labels and categories in the calendar can be altered to suit user requirements.

 The labels are defined in /var/www/html/webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225

 The categories are in /var/www/html/webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.

Zarafa Bayesian learning

This howto enables SpamAssasin Bayesian learning for Zarafa

Mail Sorting

Maildrop as configured with smeserver-mailsorting will deliver to ~/Maildir rather than zarafa

Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29,

Backup and restore

Backup

Backup is done normally with standard backup tool provided with SME, or with other backup contribs (affa). Be sure that those datas are correctly saved :

• zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok
• attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.

Restore

	Warning:
	Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version

Standard full restore function provided by SME or other backup tools will restore Zarafa datas. In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :

• stopping zarafa server

/etc/rc.d/init.d/zarafa-server stop

• deleting all tables currently into zarafa database

mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \
gawk '{print "drop table " $1 ";"}' | mysql zarafa

• import the backup of zarafa database

cd /directory/containing/your/backup
mysql < zarafa.dump

• restart zarafa server

/etc/rc.d/init.d/zarafa-server start

Bugs

Check your logs when troubleshooting or reporting bugs

tail -f /var/log/zarafa/*
tail  /var/log/slapd
tail  /var/log/messages

Please raise bugs under the SME-Contribs section in bugzilla and select the smeserver-zarafa component or use this link .

Search open bugs for smeserver-zarafa at bugs.contribs.org

Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/

---