From SME Server
Jump to navigationJump to search

PythonIcon.png 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.

Important.png Note:
This wiki page is specific to SME7 only.

There is a separate wiki page on how to manually install Zarafa 7.x on SME8 Zarafa on SME8.

There is a separate wiki page with a fully automated install of Zarafa 7.1.x on SME9 that utilizes the unix plugin Zarafa on SME 9.

Is this article helpful to you?
Please consider donating or volunteering
Thank you!


Darrell May

Stephen Noble


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


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.


Latest zarafa tested version

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

Zarafa rpms installation

Distribution: Rhel 4 = SME 7 :: Rhel 5 = SME 8

Select a version, the 3 Outlook license version, or the GPL version. (which doesn't have the zarafa-licensed-*.rpm)

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

This will also install as a dependency: sysstat

Important.png Note:
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


Important.png Note:
This is an alpha 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=smedev
config setprop zarafa-licensed status disabled #GPL version only

Important.png Note:
If you installed the GPL version only (without outlook support), you need to create the (empty) file '/var/log/zarafa/licensed.log'. This file is required in all cases. Without this file (and using the GPL non-Outlook version), the Zarafa configuration panel in server manager will not be displayed.

After rpm install execute the following:

signal-event post-upgrade; signal-event reboot

Important.png 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.


Download newer rpms, then

rpm -Uvh zarafa-6*.rpm zarafa-webaccess-*.rpm libvmime-0*.rpm libical-0*.rpm zarafa-licensed-*.rpm
signal-event post-upgrade; signal-event reboot


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



If you chose the db plugin, run:


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


Access with a browser,

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


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.


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

It seems that in the latest Thunderbird versions security tightened and Thunderbird will simply reject Self Signed Certificates when you try to connect to a (remote) SME Server on secure ports. You first must add all the secure services ports to the security exceptions of Thunderbird under:

  • tools->options->advanced->certificates->view certificates->Add Exception

and add your server address INLCUDING the specific port number of the service for EACH of the service-ports!

The format must be: (for IMAPS) (SMTP) (Caldav)
etc. etc

After accepting the self signed certificate for each service-port, you then can add an new email account and the Self Signed Certificate will not be rejected and you normally accept or install it like any other certificate.

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("", "");
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, ...

Important.png 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
https://server:8089/ical/ user's own default calendar via ical (not recommended)
https://server:8089/caldav/ user's own default calendar
https://server:8089/caldav/<other-user> 0ther-user's calendar
https://server:8089/caldav/<user>/<calendar> user's self created calendar in user's (own) store
https://server:8089/caldav/<user>/<calendar>/<subcal> user's self created subcalendar in a self created calendar
https://server:8089/caldav/public/<calendar>/ calendar folder in the public folder
URL For MAC OSX ical client
https://server:8089/caldav/ User's calendar list
https://server:8089/caldav/<other-user> Other-users calendar list
https://server:8089/caldav/public Public folders list
URL Tasks
https://server:8089/caldav/<user>/tasks user's default tasks list. ONLY WITH Zarafa 6.40.2 or newer !!

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:

Download the latest Z-push version (see:


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.


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

Customizing the Calendar

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

The labels are defined in

/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225

The categories are in

/usr/share/zarafa-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 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.
Warning.png 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


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

Zarafa: use their forum for zarafa specific bug reporting,

IDProductVersionStatusSummary (22 tasks)
7195SME Contribs8.0UNCONFIRMEDLater php53-mapi version requested
7177SME Contribs8.0UNCONFIRMEDZarafa for SME8 custom templates
6746SME Contribs8.0UNCONFIRMEDNo configuration information in Panel
6683SME Contribs8.0UNCONFIRMEDZarafa7 on SME8b6, zarafa-monitor is complaining that Terminal locale is not UTF-8
6682SME Contribs8.0UNCONFIRMEDmysql password is not properly set on SME8b6
6648SME Contribs8.0UNCONFIRMEDText-string might need review
6552SME Contribs8.0CONFIRMEDZarafa webmail mobile does not work
6459SME Contribs7.5CONFIRMEDsmeserver-zarafa package has disappeared from the smecontribs repo
6357SME Contribs7.5CONFIRMEDAdd autodiscover functionality
6305SME Contribs7.5CONFIRMEDserver_timezone parameter missing in /etc/zarafa/ical.cfg
5972SME Contribs7.4CONFIRMEDExclude non valid users and groups from unix plugin
5901SME Contribs7.4CONFIRMEDUpdate Zarafa From 6.40.RC5 to RC6 Crash the DB
5847SME Contribs7.4CONFIRMEDzarafa-install not found!
5841SME Contribs7.4CONFIRMEDConfig error with Unknown option found
5789SME Contribs8.0CONFIRMEDmapi extension not found -- error with Zarafa on sme8b5 WIP
5731SME Contribs7.4CONFIRMEDZarafa doesn't use the modSSL certificate
5667SME Contribs7.4CONFIRMEDAllow for non alphabetical characters in the fullname field
5666SME Contribs7.4CONFIRMEDAllow for non alphanumeric characters in passwords
5561SME Contribs7.4CONFIRMEDLost zarafa users after recent yum updates
5524SME Contribs7.4CONFIRMEDdelivery failure notice of big mail stuck in zarafa
5413SME Contribs7.4CONFIRMEDNo access to icals port 8089 with access=public
4886SME Contribs7.4CONFIRMEDtrigger zarafa-update on updates of zarafa* rpms