Zarafa
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
smeserver-zarafa rpm
yum install smeserver-zarafa --enablerepo=smetest
Choose which Authentication method, db, unix or ldap
http://bugs.contribs.org/show_bug.cgi?id=4873
If you choose ldap, install e-smith-base+ldap and dependencies http://wiki.contribs.org/LDAP
Run the install scripts
/etc/e-smith/events/actions/zarafa-install
Usage
Note, Mail is sent to zarafa mail stores, and NOT the users ~/Maildir
With the db method, First create a user on SME, then create a zarafa account
/etc/e-smith/events/actions/zarafa-create-user
unix and ldap automatically sync sme users
Ports
smeserver-zarafa db defaults in *-0.9.0-16 lowercase are not set with a db, the fragment gives the default if unset (SSL) are opened if service is enabled (and access is public?) zarafa-server tcpport 236 zarafa-server TCPPort 237 (SSL) zarafa-gateway pop3port 110 zarafa-gateway pop3sport 995 zarafa-gateway imapport 143 zarafa-gateway imapsport 993 zarafa-gateway TCPPort 995,993 (SSL) zarafa-ical icalport 8088 zarafa-ical TCPPort 8089 (SSL) #sme ports were changed pop(s), imap(s) and webmail are disabled /sbin/e-smith/config setprop pop3 TCPPort 8110 /sbin/e-smith/config setprop pop3s TCPPort 8995 /sbin/e-smith/config setprop imap TCPPort 8143 /sbin/e-smith/config setprop imaps TCPPort 8993
Webmail
Access with a browser, either of:
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
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
http://wiki.contribs.org/Imapsync
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/
