Difference between revisions of "Zarafa"

From SME Server
Jump to navigationJump to search
m (quick certificate conversion command added)
Line 31: Line 31:
 
  yum localinstall libvmime*.rpm libical*.rpm zarafa-6*.rpm zarafa-webaccess-6*.rpm zarafa-licensed-6*.rpm
 
  yum localinstall libvmime*.rpm libical*.rpm zarafa-6*.rpm zarafa-webaccess-6*.rpm zarafa-licensed-6*.rpm
  
==== smeserver-zarafa-0.9.0-25.noarch.rpm ====
+
==== smeserver-zarafa ====
 
{{Warning box|This is an alhpa release. Beware. For non-production testing only.}}
 
{{Warning box|This is an alhpa release. Beware. For non-production testing only.}}
{{Note box|In this rpm Zarafa and Horde/IMP can co-exist. You toggle, on a per user basis, where you want mail delivered via an accounts db entry. Default leaves mail going to users ~/Maildir for Horde/IMP.}}
+
{{Note box|From rpm -26 Zarafa and Horde/IMP can co-exist. You toggle, on a per user or global basis, where you want mail delivered via a db entry. Default leaves mail going to users ~/Maildir for Horde/IMP.}}
  
 
Note: get the rpm here:
 
Note: get the rpm here:
Line 41: Line 41:
 
Install a fresh SME 7.4 test server and perform the following:
 
Install a fresh SME 7.4 test server and perform the following:
  
  yum localinstall smeserver-zarafa-0.9.0-25.noarch.rpm
+
  yum install smeserver-zarafa --enablerepo=smetest
  
 
After rpm install execute the following:
 
After rpm install execute the following:
Line 49: Line 49:
 
{{Note box| You will be prompted to select the user plugin you wish to test. 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.}}
 
{{Note box| You will be prompted to select the user plugin you wish to test. 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.}}
  
If you chose the unix plugin, run:
+
Enable mail delivery to zarafa for users:
  
  /sbin/e-smith/db accounts setprop $USERNAME zarafa enabled
+
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
 
  /etc/e-smith/events/actions/qmail-update-user
  

Revision as of 10:31, 17 January 2009


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


Maintainers

Darrell May

Stephen Noble http://dungog.net/wiki

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

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

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


Important.png Note:
From rpm -26 Zarafa and Horde/IMP can co-exist. You toggle, on a per user or global basis, where you want mail delivered via a db entry. Default leaves mail going to users ~/Maildir for Horde/IMP.


Note: get the rpm here:

bugzilla:4891

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

yum install smeserver-zarafa --enablerepo=smetest

After rpm install execute the following:

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


Important.png Note:
You will be prompted to select the user plugin you wish to test. 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.


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

End with:

signal-event post-upgrade; signal-event reboot

Webmail

Access with a browser,

https://server/zarafa

Outlook

To use MS Outlook

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

SME and Zarafa use different folder naming.

drafts > Drafts          [client specific ?, i already have Drafts in 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 > 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");

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

If junkmail exists just delete it.

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:

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 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

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/