Difference between revisions of "Zarafa"

From SME Server
Jump to navigationJump to search
(Level)
Line 6: Line 6:
 
===Maintainer===
 
===Maintainer===
 
Darrell May
 
Darrell May
 +
 +
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===
 
===Description===

Revision as of 16:27, 22 October 2008


Zarafa for SME Server

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.


Maintainer

Darrell May

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.png 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.png Warning:
THIS IS AN ALPHA RELEASE. BEWARE. FOR NON-PRODUCTION TESTING ONLY


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

After rpm install executing two action scripts _should_ get you started:

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

Usage

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

Be aware that if you enable spamassassin sorting it goes to ~\Maildir\.junkmail, and the mailsorting contrib will sort mail into ~\Maildir folders

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

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 port's of 143 and 943 if you edit gateway.conf and disable SME's IMAP

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

Mobiles

To sync the data in zarafa to a compatible device

Not configured, todo

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

Note: SME uses 'junkmail' and Zarafa 'Junk E-mail', but don't rename junkmail as SME periodically checks for it's existence

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/