Zarafa
Zarafa for SME Server
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
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
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
Darrrels rpm, favours db method, co exist with horde
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=smedev
After rpm install executing two action scripts _should_ get you started:
/etc/e-smith/events/actions/zarafa-install
After creating a user on SME, create a zarafa account and redirect mail to zarafa with
/etc/e-smith/events/actions/zarafa-create-user
Usage
Note, Mail is sent to zarafa, and NOT the users ~/Maildir
Webmail
Access with browser for a local user
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
To access mail in Zarafa with an email client, configure your IMAP client to use port 144, or 944 for IMAPS
It's possible to use the standard IMAP ports of 143 and 993 if you edit gateway.conf and disable SME's 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.
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 Tbird/Lightning > New Calendar > on network > ical > http://<domain>:8080/ical/<user>/calendar/
8080 may change see /etc/zarafa/gateway.cfg
Note, there are problems with reading events created with /webaccess, it's a know problem and won't be fixed. Zarafa 6.30 will use CalDEV instead of iCal
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.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
Make a new template fragment:
# mkdir -p /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/ # pico /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/86Z-PushAlias
Edit the fragment and add:
Alias /Microsoft-Server-ActiveSync /var/www/html/z-push/index.php <Directory /var/www/html/z-push/> Options -Indexes AllowOverride None order allow,deny allow from all AddType application/x-httpd-php .php php_flag magic_quotes_gpc off php_flag register_globals off php_flag magic_quotes_runtime off php_flag short_open_tag on </Directory>
Expand the template:
# expand-template /etc/httpd/conf/httpd.conf
Restart httpd (the currently for Zarafa only save way):
# 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)
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/