Talk:Zarafa

From SME Server
Revision as of 02:13, 20 February 2010 by Snoble (talk | contribs) (→‎zarafa-6.40: indexing)
Jump to navigation Jump to search

Suggestions

If you can advise on standard configuration, please make it a bug so it is added to the rpm

Snoble 07:32, 22 December 2008 (UTC)


smeserver-zarafa-0.9-48

/etc/e-smith/events/actions/zarafa-services-stop has been removed

/etc/e-smith/events/actions/zarafa-services
Usage: start|stop|restart|enabled|disabled

start services
stop services
restart services
enabled - set db values to enabled, zarafa will start on reboot
disabled - set db values to disabled, zarafa won't start on reboot


InnoDB support is enabled automatically

zarafa-6.40

yum localinstall libvmime-0*.rpm libical-0*.rpm zarafa-*.rpm catdoc-*.rpm

indexing service

The catdoc-rpm is needed for the new indexing service that is introduced with Zarafa 6.40... but the indexing-service is not yet handled by smeserver-zarafa. --jester 15:42, 13 February 2010 (UTC)

the catdoc rpm has un meet dependencies on SME 7 so it's only listed on discussion not the main page, and yes it's not implemented yet

it would help if you could check which config file it was in, the relevant line and raise a bug

Snoble 01:13, 20 February 2010 (UTC)

SME 8 beta

php 5.2.10

The php mapi files zarafa uses are compiled against 5.1.6, if sme 8 uses 5.2.10 we have a problem

here is one workaround http://forums.zarafa.com/viewtopic.php?f=9&t=3263&p=18753#p18753

Upgrade to Zarafa 6.30

Is there anything here we need to keep
I like the signal-event pre-backup suggestion 
stephen

The new Zarafa 6.30 version has some interesting new features with the most interesting one CALDAV support.


As a precausion backup the MySQL database (files we be placed in: /home/e-smith/db/mysql/):

 signal-event pre-backup

Download the new version from the Zarafa website (rhel4 / i386 / 3 Outlook license (or GPL)) and extract it: http://www.zarafa.com/download-community

 tar -zxvf zarafa-6.30-rhel4-i386.tar.gz

Stop the Zarafa server:

 /etc/e-smith/events/actions/zarafa-services-stop
 yum localinstall  zarafa-6*.rpm zarafa-webaccess-6*.rpm libical*.i386.rpm libvmime*.i386.rpm zarafa-licensed-6*.rpm (last not required for GPL)

To regenerate the configuration files:

 /etc/e-smith/events/actions/zarafa-services start

With this new version some database conversions need to be done, This process must not be interrupted! So we will start the server and tail the server.log for this process to complete:

 /etc/init.d/zarafa-server start
 tail -f /var/log/zarafa/server.log

You'll see some messages about creating and updating tables... wait until you see the 'Startup succeeded' message (see example output below). This process can take a fair amount of time if you have a lot of users and/or big mailboxes, or a few seconds for light use.

 Start: Adding externid to 'object' table
 Done: Adding externid to 'object' table
 Start: Creating Single Instance Attachment table
 Done: Creating Single Instance Attachment table
 Start: Locking multiserver capability
 Done: Locking multiserver capability
 Start: Creating Addressbook Changes table
 Done: Creating Addressbook Changes table
 Start: Updating 'singleinstances' table to correct tag value
 Done: Updating 'singleinstances' table to correct tag value
 Listening for pipe connections on /var/run/zarafa
 Listening for TCP connections on port 237
 Startup succeeded on pid 22957

To finish things off:

 signal-event post-upgrade ; signal-event reboot

N.B. I updated my test box yesterday (07/25). In testing CalDAV from iCal, I found issues in the ical.log and the client would not connect to the calendar. I've raised it on the Zarafa forums. Des Dougan.