3,250
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + + + + − + − + + + + + + + + + + + − 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 − + + + + + − + + + + + + + + + + + + + + + − 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 box|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 − + + + + + + + + + + + + + + + + + + + + + + + + − ===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 − + − http://server/zarafa+ + + − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − 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+ Line 95:
Line 272: − =====Folder Naming===== − SME and Zarafa use different folder naming. To enhance migration SME folders should be renamed prior to migration. − drafts > Drafts+ − junkmail > Junk E-mail − sent-mail > Sent Items − trash > Deleted Items − 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+ − wget http://dag.wieers.com/rpm/packages/perl-Mail-IMAPClient/perl-Mail-IMAPClient-2.2.9-1.2.el4.rf.noarch.rpm+ − yum localinstall perl-Mail-IMAPClient-2.2.9-1.2.el4.rf.noarch.rpm+ + − wget http://www.linux-france.org/prj/imapsync/dist/imapsync-1.264.tgz+ − tar -zxvf imapsync-1.264.tgz − cd ./imapsync-1.264 − make install − 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 === − + + + + + − Zarafa use their forum for bug reporting, http://forums.zarafa.com/ − + + + +
no edit summary
{{Languages}}
{{Languages|Zarafa}}
{{Level|advanced}}
{{Note box|
'''This wiki page is specific to SME7 only.'''
===Maintainer===
'''There is a separate wiki page on how to manually install Zarafa 7.x on SME8 [[Zarafa on SME8]].'''
{{Incomplete}}
'''There is a separate wiki page with a ''fully automated'' install of Zarafa 7.1.x on SME9 that utilizes the unix plugin [[Zarafa on SME 9]].'''
}}
{{usefulnote}}
===Maintainers===
Darrell May
Stephen Noble http://dungog.net/wiki
=== Version ===
{{#smeversion:smeserver-zarafa}}
===Description===
===Description===
http://www.zarafa.com
http://www.zarafa.com
Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft
Outlook, which enables the sharing of mail and appointments from Outlook and a
web-based interface.
===Installation===
===Installation===
====Download & Install Zarafa rpms====
==== Latest zarafa tested version ====
Information on previous versions of zarafa rpms can be found in the [http://download.zarafa.com/zarafa/release/docs/changelog.en.txt changelog document]
==== Zarafa rpms installation ====
http://www.zarafa.com/download-community
http://www.zarafa.com/download-community
Distribution = Rhel 4
Distribution: Rhel 4 = SME 7 :: Rhel 5 = SME 8
Select a version, the 3 Outlook license version, or the GPL version. (which doesn't have the zarafa-licensed-*.rpm)
tar -zxvf zarafa-6.*.tar.gz
yum localinstall libvmime-0*.rpm libical-0*.rpm zarafa-6*.rpm zarafa-webaccess-*.rpm zarafa-licensed-*.rpm
This will also install as a dependency: ''sysstat''
{{Note box| You have to enable InnoDB support in MySql in order to get zarafa-server running, for information on how to do so, see [[MySQL#Enable_InnoDB_engine]]}}
==== smeserver-zarafa ====
{{Note box| This is an alpha release. Possibly for production servers after testing with per user settings first.
You select 'per user' or 'globally' where you want mail delivered via db entries. Default leaves mail going to users ~/Maildir.
A minimal amount of disruption can be achieved by enabling per user, that user just enables another IMAP connection in their email client on port 8143, they could then just drag and drop mail between SME to Zarafa mail stores. }}
Install a fresh SME 7.4 test server and perform the following:
yum install smeserver-zarafa --enablerepo=smedev
config setprop zarafa-licensed status disabled #GPL version only
{{Note box|If you installed the GPL version only (without outlook support), you need to create the (empty) file '/var/log/zarafa/licensed.log'. This file is required in all cases. Without this file (and using the GPL non-Outlook version), the Zarafa configuration panel in server manager will not be displayed.}}
After rpm install executing two action scripts _should_ get you started:
After rpm install execute the following:
/etc/e-smith/events/actions/zarafa-install
/etc/e-smith/events/actions/zarafa-install
signal-event post-upgrade; signal-event reboot
{{Note box| You will be prompted to select the user plugin you wish to test. We suggest the db method. 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.}}
==== Updating ====
Download newer rpms, then
rpm -Uvh zarafa-6*.rpm zarafa-webaccess-*.rpm libvmime-0*.rpm libical-0*.rpm zarafa-licensed-*.rpm
/etc/e-smith/events/actions/zarafa-update
signal-event post-upgrade; signal-event reboot
===Usage===
====Managing Users====
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
/etc/e-smith/events/actions/zarafa-create-user
or manage zarafa users with the panel ( smeserver-zarafa >= 0.29 )
====Webmail====
====Webmail====
Access with browser for a local user
Access with a browser,
https://server/zarafa
https://server/webaccess
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')
====Outlook====
====Outlook====
To use MS Outlook
To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz
* Outlook 2007 client generates ''Error 0x80070057'' on send and receive if the Zarafa
server is added to an existing profile. Creating a new clean profile solved
the problem.
====IMAP====
The default ports for Zarafa are 8000 + default values
so imap = 8143, imaps 8993
SME and Zarafa use different folder naming.
drafts > Drafts [client specific ?, Drafts is default Thunderbird-2.0]
sent-mail > Sent Items
trash > Deleted Items
junkmail > Junk E-mail
=====Thunderbird=====
It seems that in the latest Thunderbird versions security tightened and Thunderbird will simply reject Self Signed Certificates when you try to connect to a (remote) SME Server on secure ports.
You first must add all the secure services ports to the security exceptions of Thunderbird under:
* tools->options->advanced->certificates->view certificates->Add Exception
and add your server address INLCUDING the specific port number of the service for EACH of the service-ports!
The format must be:
https://yourserver.com:8993 (for IMAPS)
https://yourserver.com:465 (SMTP)
https://yourserver.com:8089 (Caldav)
etc. etc
After accepting the self signed certificate for each service-port, you then can add an new email account and the Self Signed Certificate will not be rejected and you normally accept or install it like any other certificate.
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 and add new string as below
user_pref("mail.server.server5.port", "8143");
user_pref("mail.server.server5.name", "zac@232.net");
user_pref("mail.server.server5.numHdrsToKeep", 30);
user_pref("mail.server.server5.timeout", 29);
right click > new
preference name > mail.server.server5.trash_folder_name
value > Deleted Items
+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 CalDAV / iCal ====
Starting from Zarafa 6.30 there is decent CalDAV/iCal support for calendars (tasks not yet) that can be accessed with an CalDAV or iCal client eg, Thunderbird with Lighting, Sunbird, Evolution, MAC ical, ...
{{Note box|Currently there is a bug in smeserver-zarafa package (bug #5410) that might prevent you from accessing the calendar. If so, replicate the steps described in the bug report to correct this and issue the following command from the commandline and you should be good to go: <tt>/etc/init.d/zarafa-ical restart</tt>}}
* In Thunderbird/Lightning: New Calendar > on network > CalDAV > Location: see table below
* In Evolution: New Calendar > Type: CalDAV > URL: see table below (remove the 'Use SSL' option)
* In Mac iCal client: iCal > Preferences > click '+' > Account URL: see table below
{| align="center" {{Prettytable}}
|-
|{{Hl3}}|'''URL'''
|{{Hl3}}|'''Calendar'''
|-
|<nowiki>https://server:8089/ical/</nowiki>
|user's own default calendar via ical (not recommended)
|-
|<nowiki>https://server:8089/caldav/</nowiki>
|user's own default calendar
|-
|<nowiki>https://server:8089/caldav/<other-user></nowiki>
|0ther-user's calendar
|-
|<nowiki>https://server:8089/caldav/<user>/<calendar></nowiki>
|user's self created calendar in user's (own) store
|-
|<nowiki>https://server:8089/caldav/<user>/<calendar>/<subcal></nowiki>
|user's self created subcalendar in a self created calendar
|-
|<nowiki>https://server:8089/caldav/public/<calendar>/</nowiki>
|calendar folder in the public folder
|-
|colspan="2" {{Hl3}}|'''URL For MAC OSX ical client'''
|-
|<nowiki>https://server:8089/caldav/</nowiki>
|User's calendar list
|-
|<nowiki>https://server:8089/caldav/<other-user></nowiki>
|Other-users calendar list
|-
|<nowiki>https://server:8089/caldav/public</nowiki>
|Public folders list
|-
|{{Hl3}}|'''URL'''
|{{Hl3}}|'''Tasks'''
|-
|-
|<nowiki>https://server:8089/caldav/<user>/tasks</nowiki>
|user's default tasks list. '''ONLY WITH Zarafa 6.40.2 or newer !!'''
|-
|}
Port 8089 is used for secure SSL connections, port 8088 for unsecured connections.
====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.2.tar.gz
Extract the files:
tar -zxvf z-push-1.2.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 SSL connection / mail-push is working.
Tested and working with WinMobile 6.1 on an upgraded QTEK9100 over SSL connection. Push mail not tested.
Tested and working with WinMobile 2003 on an QTEK9090 over SSL connection. Push mail not tested.
Tested and working with IPHONE. Push mail not tested.
Tested and working with Nokia 6120 Classic. Push mail not tested.
=== Extras ===
=== Extras ===
====Migrating users and data to Zarafa====
====Migrating users and data to Zarafa====
http://wiki.contribs.org/Imapsync
====Customizing the Calendar====
The labels and categories in the calendar can be altered to suit user requirements.
The labels are defined in
/usr/share/zarafa-webaccess/client/layout/dialogs/standard/appointment.php beginning at line 225
The categories are in
/usr/share/zarafa-webaccess/client/layout/dialogs/modal/categories.php beginning at line 51.
==== Zarafa Bayesian learning ====
This howto enables SpamAssasin [[:Zarafa Bayesian Learning | Bayesian learning for Zarafa]]
==== Mail Sorting ====
Maildrop as configured with
[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa
Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29,
==== Backup and restore ====
===== Backup =====
Backup is done normally with [[SME_Server:Documentation:Administration_Manual:Chapter10|standard backup tool]] provided with SME, or with other backup contribs ([[affa]]). Be sure that those datas are correctly saved :
*zarafa database. All backup tools are saving all mysql database in standard mode, it should be Ok
*attachment files. Those one are stored in '/home/e-smith/files/zarafa' directory.
===== Restore =====
{{Warning box| Database restoring has been tested when facing an issue during upgrade of zarafa from 6.20 to 6.20.4. No problems were detected, meaning there is no compatibility issues between those 2 versions. It should not be the case with every version}}
Standard full restore function provided by SME or other backup tools will restore Zarafa datas.
In certain cases, it is interessant to restore only zarafa database backup (ie update issue). This is done following those steps :
*stopping zarafa server
/etc/rc.d/init.d/zarafa-server stop
*deleting all tables currently into zarafa database
mysql zarafa -e "show tables" | grep -v Tables_in | grep -v "+" | \
gawk '{print "drop table " $1 ";"}' | mysql zarafa
*import the backup of zarafa database
cd /directory/containing/your/backup
mysql < zarafa.dump
* restart zarafa server
/etc/rc.d/init.d/zarafa-server start
=== 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 {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.
Please raise bugs under the SME-Contribs section in {{BugzillaFileBug|product=|component=|title=bugzilla}}and select the smeserver-zarafa component or use {{BugzillaFileBug|product=SME%20Contribs|component=smeserver-zarafa|title=this link}}.
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=SME+Contribs&component=smeserver-zarafa&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=Open Search open bugs] for smeserver-zarafa at bugs.contribs.org
[http://bugs.contribs.org/buglist.cgi?query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&value0-0-0=Open&component=smeserver-zarafa&product=SME%20Contribs Search open bugs] for smeserver-zarafa at bugs.contribs.org
Zarafa: use their forum for zarafa specific bug reporting, http://forums.zarafa.com/
[[Category: Contrib]]
{{#bugzilla:columns=id,product,version,status,summary |sort=id|order=desc |component=smeserver-zarafa|noresultsmessage="No open bugs found."}}
----
[[Category: Deprecated Contrib]]
[[Category: Groupware]]