Difference between revisions of "Zarafa"

From SME Server

Latest revision as of 07:08, 18 April 2021

Languages:

	Skill level: advanced
	The instructions on this page may require deviations from standard procedures. A good understanding of linux and Koozali SME Server is recommended.

Note:

This wiki page is specific to SME7 only.

There is a separate wiki page on how to manually install Zarafa 7.x on SME8 Zarafa on SME8.

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.

Is this article helpful to you?
Please consider donating or volunteering
Thank you!

Maintainers

Darrell May

Stephen Noble http://dungog.net/wiki

Version

smeserver-zarafa

The latest version of smeserver-zarafa is available in the SME repository, click on the version number(s) for more information.

Description

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

Latest zarafa tested version

Information on previous versions of zarafa rpms can be found in the changelog document

Zarafa rpms installation

http://www.zarafa.com/download-community

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

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:
	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 execute the following:

/etc/e-smith/events/actions/zarafa-install
signal-event post-upgrade; signal-event reboot

Note:

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

or manage zarafa users with the panel ( smeserver-zarafa >= 0.29 )

Webmail

Access with a browser,

https://server/zarafa
https://server/webaccess
https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')

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:
	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: `/etc/init.d/zarafa-ical restart`

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

URL	Calendar
https://server:8089/ical/	user's own default calendar via ical (not recommended)
https://server:8089/caldav/	user's own default calendar
https://server:8089/caldav/<other-user>	0ther-user's calendar
https://server:8089/caldav/<user>/<calendar>	user's self created calendar in user's (own) store
https://server:8089/caldav/<user>/<calendar>/<subcal>	user's self created subcalendar in a self created calendar
https://server:8089/caldav/public/<calendar>/	calendar folder in the public folder
URL For MAC OSX ical client
https://server:8089/caldav/	User's calendar list
https://server:8089/caldav/<other-user>	Other-users calendar list
https://server:8089/caldav/public	Public folders list
URL	Tasks
https://server:8089/caldav/<user>/tasks	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

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

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 Bayesian learning for Zarafa

Mail Sorting

Maildrop as configured with 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 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:
	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 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/

ID	Product	Version	Status	Summary (22 tasks) ⇒
7195	SME Contribs	8.0	UNCONFIRMED	Later php53-mapi version requested
7177	SME Contribs	8.0	UNCONFIRMED	Zarafa for SME8 custom templates
6746	SME Contribs	8.0	UNCONFIRMED	No configuration information in Panel
6683	SME Contribs	8.0	UNCONFIRMED	Zarafa7 on SME8b6, zarafa-monitor is complaining that Terminal locale is not UTF-8
6682	SME Contribs	8.0	UNCONFIRMED	mysql password is not properly set on SME8b6
6648	SME Contribs	8.0	UNCONFIRMED	Text-string might need review
6552	SME Contribs	8.0	CONFIRMED	Zarafa webmail mobile does not work
6459	SME Contribs	7.5	CONFIRMED	smeserver-zarafa package has disappeared from the smecontribs repo
6357	SME Contribs	7.5	CONFIRMED	Add autodiscover functionality
6305	SME Contribs	7.5	CONFIRMED	server_timezone parameter missing in /etc/zarafa/ical.cfg
5972	SME Contribs	7.4	CONFIRMED	Exclude non valid users and groups from unix plugin
5901	SME Contribs	7.4	CONFIRMED	Update Zarafa From 6.40.RC5 to RC6 Crash the DB
5847	SME Contribs	7.4	CONFIRMED	zarafa-install not found!
5841	SME Contribs	7.4	CONFIRMED	Config error with Unknown option found
5789	SME Contribs	8.0	CONFIRMED	mapi extension not found -- error with Zarafa on sme8b5 WIP
5731	SME Contribs	7.4	CONFIRMED	Zarafa doesn't use the modSSL certificate
5667	SME Contribs	7.4	CONFIRMED	Allow for non alphabetical characters in the fullname field
5666	SME Contribs	7.4	CONFIRMED	Allow for non alphanumeric characters in passwords
5561	SME Contribs	7.4	CONFIRMED	Lost zarafa users after recent yum updates
5524	SME Contribs	7.4	CONFIRMED	delivery failure notice of big mail stuck in zarafa
5413	SME Contribs	7.4	CONFIRMED	No access to icals port 8089 with access=public
4886	SME Contribs	7.4	CONFIRMED	trigger zarafa-update on updates of zarafa* rpms

Retrieved from "https://wiki.koozali.org/index.php?title=Zarafa&oldid=39920"

Categories:

@@ Line 1: / Line 1: @@
-{{Languages}}
+{{Languages|Zarafa}}
-{{Level|developer}}
+{{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]].'''
-Darrell May, Stephen Noble
-Nothing here is irreversible ;)
+'''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
-We use imapsync to move e-mail into Zarafa. We can use imapsync to move e-mail back into SME.
+Stephen Noble http://dungog.net/wiki
+=== Version ===
+{{#smeversion:smeserver-zarafa}}
 ===Description===
 http://www.zarafa.com
-Open Source Collaboration, providing:
+Zarafa is a workgroup sharing solution based on the look-and-feel of Microsoft
-:Integration with your existing Linux mailserver
+Outlook, which enables the sharing of mail and appointments from Outlook and a
-:Native mobile phone support
+web-based interface.
-: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}}
-====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
-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.
- tar -zxvf zarafa-6.20-rhel4-i386.tar.gz
+You select 'per user' or 'globally' where you want mail delivered via db entries. Default leaves mail going to users ~/Maildir.
- yum localinstall libvmime*.rpm libical*.rpm zarafa-6*.rpm zarafa-webaccess-6*.rpm zarafa-licensed-6*.rpm
+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. }}
-====Download & Install alpha smeserver-zarafa rpm====
+Install a fresh SME 7.4 test server and perform the following:
-{{Warning box|This is an alhpa release. Beware. For non-production testing only.}}
-  yum install smeserver-zarafa --enablerepo=smetest
+  yum install smeserver-zarafa --enablerepo=smedev
+ config setprop zarafa-licensed status disabled #GPL version only
-Choose which Authentication method, db, unix or ldap
+{{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.}}
- http://bugs.contribs.org/show_bug.cgi?id=4873
-Run the install scripts
+After rpm install execute the following:
   /etc/e-smith/events/actions/zarafa-install
+ signal-event post-upgrade; signal-event reboot
-With the db method, First create a user on SME, then create a zarafa account
+{{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.}}
-  /etc/e-smith/events/actions/zarafa-create-user
+==== 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===
-Note, Mail is sent to zarafa, and NOT the users ~/Maildir
+====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
-SME pop, imap and horde webmail is disabled
+If you chose the db plugin, run:
+ /etc/e-smith/events/actions/zarafa-create-user
+or manage zarafa users with the panel ( smeserver-zarafa >= 0.29 )
-Standard mail ports are used by Zarafa
 ====Webmail====
-Access with a browser, either of:
+Access with a browser,
-: http://server/zarafa
+ https://server/zarafa
-: http://server/webmail
+ https://server/webaccess
-: http://server/webaccess
+ https://server/webmail (with Horde disabled '/server-manager > Email > Webmail Access')
 ====Outlook====
-To use MS Outlook
+To use MS Outlook install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz
-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 2007 client generates ''Error 0x80070057'' on send and receive if the Zarafa
-=====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 default ports for Zarafa are 8000 + default values
+so imap = 8143, imaps 8993
-====IMAP====
+SME and Zarafa use different folder naming.
-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 [http://kb.mozillazine.org/IMAP_Trash_folder] for details.
+ 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 > new string as below
+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");
-====Calendar====
+Drafts and Sent Items can be changed in : Account Settings > user > Copies and Folders
-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/
+If junkmail exists just delete it.
-for SSL
+==== 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>}}
-Note, there were problems with reading events created with /webaccess, seems better with RC1
+* 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
-it's a know problem. Zarafa 6.30 will use CalDEV instead of iCal
+{| 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====
@@ Line 104: / Line 212: @@
 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
+  wget http://download2.berlios.de/z-push/z-push-1.2.2.tar.gz
 Extract the files:
-  # tar -zxvf z-push-1.2.tar.gz -C /var/www/html
+  tar -zxvf z-push-1.2.2.tar.gz -C /var/www/html
 'State'-dir needs to be writable for apache:
-  # cd /var/www/html/z-push/
+  chmod 755 /var/www/html/z-push/state
- # chmod 755 state
+  chown www:www /var/www/html/z-push/state
-  # chown www:www state
 Expand and restart
@@ Line 119: / Line 226: @@
 =====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.
+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.
@@ Line 125: / Line 232: @@
 Here are the steps to add your server as a trusted platform on your WM6 mobile :
-. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer
-. we need to transform those .crt certificates to .cer certificate ( same type of certificate but .crt are text-encoded ). To do so :
+. 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
+. copy your server's certificates located in /home/e-smith/ssl.crt/ on a Windows XP/Vista computer
+. 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"
@@ Line 139: / Line 251: @@
 =====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 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 ===
@@ Line 153: / Line 272: @@
 ====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              ## we should write a script, foreach user, mv folder, both ways
+http://wiki.contribs.org/Imapsync
- 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.
+====Customizing the Calendar====
-http://download.zarafa.com/zarafa/release/docs/zarafa_migration.en.pdf
+The labels and categories in the calendar can be altered to suit user requirements.
-=====IMAP migration from SME/IMAP to Zarafa/IMAP=====
+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.
-Configure zarafa-gateway for migration enabling IMAP on port 144 only as shown above
+==== Zarafa Bayesian learning ====
-Get imapsync and required perl module
+This howto enables SpamAssasin [[:Zarafa Bayesian Learning‎ | Bayesian learning for Zarafa]]
-http://wiki.contribs.org/Imapsync
+==== Mail Sorting ====
+Maildrop as configured with
+[http://www.dungog.net/wiki/Smeserver-mailsorting smeserver-mailsorting] will deliver to ~/Maildir rather than zarafa
-Perform a user mail sync from SME/IMAP (host1/port1) to Zarafa/IMAP (host2/port2) [NOTE, ports have changed]
+Procmail will sort to zarafa for enabled users from smeserver-mailsorting-1.2-29,
-  imapsync --noauthmd5 --host1 localhost --port1 143 --user1 <username> --password1 <password> --sep2 / --prefix2 "" --host2 localhost --port2 144 --user2 <username> --password2 <password>
+==== 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.
-Example to synchronize a user named 'bob' with password 'bob123' from SME IMAP into Zarafa:
+===== 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}}
-  imapsync --noauthmd5 --host1 localhost --port1 143 --user1 bob --password1 bob123 --sep2 / --prefix2 "" --host2 localhost --port2 144 --user2 bob --password2 bob123
+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
-After syncing is complete, stop zarafa-gateway service and/or edit /etc/zarafa/gateway.cfg to meet your needs.
+=== Bugs ===
+Check your logs when troubleshooting or reporting bugs
+ tail -f /var/log/zarafa/*
+ tail  /var/log/slapd
+ tail  /var/log/messages
-=== Bugs ===
 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/
-Zarafa use their forum for 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]]

Difference between revisions of "Zarafa"

Latest revision as of 07:08, 18 April 2021

Maintainers

Version

Description

Installation

Latest zarafa tested version

Zarafa rpms installation

smeserver-zarafa

Updating

Usage

Managing Users

Webmail

Outlook

IMAP

Thunderbird

Calendar CalDAV / iCal

Mobile synchronisation

SSL Synchronization with Windows Mobile devices

Know working hardware

Extras

Command line admin

Migrating users and data to Zarafa

Customizing the Calendar

Zarafa Bayesian learning

Mail Sorting

Backup and restore

Backup

Restore

Bugs

Navigation menu

Search