Zarafa

Languages:

English  • français

	Skill level: developer
	Risk of inconsistencies with Koozali SME Server methodology, upgrades & functionality is high. One must be knowledgeable about how changes impact their Koozali SME Server. Significant risk of irreversible harm.

Maintainer

Darrell May, Stephen Noble

Nothing here is irreversible ;)

We use imapsync to move e-mail into Zarafa. We can use imapsync to move e-mail back into SME.

Description

http://www.zarafa.com

Open Source Collaboration, providing:

Integration with your existing Linux mailserver

Native mobile phone support

Outlook "Look & Feel" webaccess

Stable Outlook sharing (100% MAPI) - MS Exchange replacement

The Community version http://forums.zarafa.com/viewtopic.php?f=7&t=990

Installation

	Incomplete:
	This article or section needs to be expanded. Please help to fill the gaps or discuss the issue on the talk page

Download & Install Zarafa rpms

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

Distribution = Rhel 4

tar -zxvf zarafa-6.20-rhel4-i386.tar.gz

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

Download & Install alpha smeserver-zarafa rpm

	Warning:
	This is an alhpa release. Beware. For non-production testing only.

Darrrels rpm, favours db method, co exist with horde [the rest of the wiki refers to stephens rpm]

http://mirror.contribs.org/smeserver/contribs/dmay/smeserver/7.x/ > smeserver-zarafa-0.9-XX.noarch.rpm
yum localinstall smeserver-zarafa-0.9-XX.noarch.rpm

Stephens rpm, favours unix or ldap, aims to replace horde

yum install smeserver-zarafa --enablerepo=smetest

Choose which Authentication method, db, unix or ldap

http://bugs.contribs.org/show_bug.cgi?id=4873

Run the install scripts

/etc/e-smith/events/actions/zarafa-install

With the db method, First create a user on SME, then create a zarafa account

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

Usage

Note, Mail is sent to zarafa, and NOT the users ~/Maildir

SME pop, imap and horde webmail is disabled

Standard mail ports are used by Zarafa

Webmail

Access with browser for a local user

http://server/zarafa

Outlook

To use MS Outlook

Configure, enable and start /etc/init.d/zarafa-licensed

Install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz

Outlook Client Send/Recieve Error 0x80070057

Outlook 2007 client generates the above error on send and receive if the Zarafa server is added to an existing profile. Creating a new clean profile solved the problem.

http://forums.zarafa.com/viewtopic.php?f=12&t=1048

IMAP

The Thunderbird client uses its own Trash folder, not the Zarafa "Deleted Items" folder. This can be changed by editing the prefs.js profile file. See this Mozilla how-to [1] for details.

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

user_pref("mail.server.server5.name", "zac@232.net");
user_pref("mail.server.server5.numHdrsToKeep", 30);
user_pref("mail.server.server5.timeout", 29);
+user_pref("mail.server.server5.trash_folder_name", "Deleted Items");

Calendar

To access the calendar functions with an iCal client eg, Thunderbird and Lighting

in Thunderbird/Lightning > New Calendar > on network > ical > http://<domain>:8088/ical/<user>/calendar/

8089 for SSL

Note, there were problems with reading events created with /webaccess, seems better with RC1

it's a know problem. Zarafa 6.30 will use CalDEV instead of iCal

Mobile synchronisation

	Warning:
	Please check the code for errors and security issues.

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.tar.gz

Extract the files:

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

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

# cd /var/www/html/z-push/
# chmod 755 state
# chown www:www 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 securised connection is possible if you can add your site as a trusted one with corresponding certificate.

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. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer

2. 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 NON SSL connection (mail-push not yet tested). Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. 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

Folder Naming

SME and Zarafa use different folder naming. To enhance migration SME folders should be renamed prior to migration.

drafts > Drafts
sent-mail > Sent Items
trash > Deleted Items
junkmail > Junk E-mail

Zarafa migration whitepaper describes various ways of migrating your users and your data to a Zarafa server.

http://download.zarafa.com/zarafa/release/docs/zarafa_migration.en.pdf

IMAP migration from SME/IMAP to Zarafa/IMAP

Configure zarafa-gateway for migration enabling IMAP on port 144 only as shown above

Get imapsync and required perl module

http://wiki.contribs.org/Imapsync

Perform a user mail sync from SME/IMAP (host1/port1) to Zarafa/IMAP (host2/port2) [NOTE, ports have changed]

imapsync --noauthmd5 --host1 localhost --port1 143 --user1 <username> --password1 <password> --sep2 / --prefix2 "" --host2 localhost --port2 144 --user2 <username> --password2 <password>

Example to synchronize a user named 'bob' with password 'bob123' from SME IMAP into Zarafa:

imapsync --noauthmd5 --host1 localhost --port1 143 --user1 bob --password1 bob123 --sep2 / --prefix2 "" --host2 localhost --port2 144 --user2 bob --password2 bob123

After syncing is complete, stop zarafa-gateway service and/or edit /etc/zarafa/gateway.cfg to meet your needs.

Bugs

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 bug reporting, http://forums.zarafa.com/