Changes

Jump to navigation Jump to search
4,471 bytes added ,  08:26, 4 October 2011
m
Added information on updating php-mapi if upgraded php to version 5.3
Line 1: Line 1: −
== Rough Guide to get Zarafa running. Lots more to do... ==
+
=== Zarafa7 on SME8 ===
http://forums.contribs.org/index.php?topic=42118.0
+
If you want to test the new Zarafa 7 version on SME8b6: install as described [[Zarafa | here]], download the needed files from [[bugzilla:5789]] => Comment#5 and extract as described, make the following symbolic links and restart apache:
 +
ln -s /lib/libcrypto.so.0.9.8e /usr/lib/libcrypto.so.0.9.8
 +
ln -s /lib/libssl.so.0.9.8e /usr/lib/libssl.so.0.9.8
 +
sv t httpd-e-smith
   −
===Download & Install===
+
=== Dependancies ===
   −
http://www.zarafa.com/download-community
+
Here are links to all the dependencies that I used for version 7.0.1.28479 (free):
 +
libicu - ftp://ftp.pbone.net/mirror/ftp.centos.org/5.7/os/i386/CentOS/libicu-3.6-5.16.i386.rpm
 +
poppler-utils - ftp://ftp.pbone.net/mirror/ftp.centos.org/5.7/os/i386/CentOS/poppler-utils-0.5.4-4.4.el5_6.17.i386.rpm
 +
poppler - ftp://ftp.pbone.net/mirror/ftp.centos.org/5.7/os/i386/CentOS/poppler-0.5.4-4.4.el5_6.17.i386.rpm
 +
hicolor-icon-theme - ftp://ftp.pbone.net/mirror/ftp.centos.org/5.7/os/i386/CentOS/hicolor-icon-theme-0.9-2.1.noarch.rpm
 +
bitstream-vera-fonts - ftp://ftp.pbone.net/mirror/ftp.centos.org/5.7/os/i386/CentOS/bitstream-vera-fonts-1.10-7.noarch.rpm
 +
w3m - ftp://ftp.pbone.net/mirror/ftp.centos.org/5.7/os/i386/CentOS/w3m-0.5.1-18.el5.i386.rpm
   −
Distribution = Rhel 4
+
If you are upgrading from version 6 you will also need these dependencies:
 +
MySQL-python - ftp://ftp.pbone.net/mirror/ftp.centos.org/5.7/os/i386/CentOS/MySQL-python-1.2.1-1.i386.rpm
 +
mx - http://mirror.centos.org/centos/5/os/i386/CentOS/mx-2.0.6-2.2.2.i386.rpm
   −
tar -zxvf zarafa-6.20-rhel4-i386.tar.gz
+
- Garth Kirkwood (girkers)
   −
yum localinstall libvmime*.rpm
+
=== Installation ===
yum localinstall libical*.rpm
  −
yum localinstall zarafa-6*.rpm
  −
yum localinstall zarafa-webaccess-6*.rpm
     −
===Create the Database===
+
To make things a bit more easy for non Zarafa experts, I used this procedure for a clean install.
 +
Get zcp 7.01, unpack, remove the devel packages and install all rpm's:
 +
yum localinstall *.rpm
 +
All packages have dependencies that cannot be resolved if you install only part of the rpm's (as suggested installation instruction for zcp 6.40).
   −
mysqladmin create zarafa
+
Then install smeserver-zarafa. I could not retrieve this file from the smevdev repository (sme8 uses another one?).
  mysql -e "grant all privileges on zarafa.* to zarafa@localhost identified by 'yourpassword'"
+
Get it manually and install:
  mysql -e "flush privileges"
+
  wget http://ftp.nluug.nl/os/Linux/distr/smeserver/releases/7/smedev/i386/RPMS/smeserver-zarafa-0.9.0-53.el4.sme.noarch.rpm
 +
  yum localinstall smeserver-zarafa-0.9.0-53.el4.sme.noarch.rpm
   −
===Zarafa config files===
+
/etc/e-smith/events/actions/zarafa-install
   −
  nano /etc/zarafa/server.cfg
+
expand the php-mapi patch patch and and the symbolic links (see first text block above: Zarafa7 on SME8).
  mysql_user = zarafa
+
 
  mysql_password = 'yourpassword'
+
If you use webaccess mobile, change 86ZarafaAlias template [[bugzilla:6552]]
  mysql_database = zarafa
+
 
 +
If you use z-push, download and install (see [[Zarafa | here]] mobile synchronization).
 +
You have to change the name of the installation folder from z-push<version #> to z-push, because this is expected by the smeserver-zarafa package.
 +
The download extracts correctly but leaves the file and group ownership to some unknown user 33. I changed that (might not be necessary, I consider it a small security risk).
 +
  chown -R root:root /var/www/html/z-push
 +
 
 +
Then post-upgrade and restart.
 +
 
 +
For upgrades (tested with 6.40.2): zarafa-server does not start, there is an  error message in the /var/log/zarafa/zarafa-server.log file which tells you to update the database first. A python script is provided to do just that. See also [[http://doc.zarafa.com/7.0/Administrator_Manual/en-US/html/upgrading.html zarafa administration manual]]!
 +
Stop running zarafa services, make sure a backup of the zarafa mysql database exists, install MySQL-python, run update script.
 
   
 
   
  user_plugin        = unix
+
yum install MySQL-python
  user_plugin_config = /etc/zarafa/unix.cfg
     −
  nano /etc/zarafa/unix.cfg
+
  python /usr/share/doc/zarafa/zarafa7-upgrade
  default_domain = yourserver.net
  −
  min_user_uid = 5000
  −
  min_group_gid = 5000
     −
===SME templates===
+
Reports the script failes with wrong inno_db settings for mysql are on the zarafa forums. So verify your local MySQL innodb settings match the required values [[http://doc.zarafa.com/7.0/Administrator_Manual/en-US/html/_memory_usage_setup.html zarafa administration manual]]). 
   −
====httpd.conf====
+
===Sogo===
   −
mkdir -p /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf
+
FYI, I'm now using [[Sogo]] instead of zarafa, hence I have stopped work on smeserver-zarafa.
   −
nano /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/86ZarafaAlias
+
Sogo may not be as complete as zarafa, but is simpler to intergrate/maintain and will likely have a wider usage.
  Alias /zarafa /var/www/html/webaccess/
  −
  <Directory /var/www/html/webaccess/>
  −
  Options -Indexes
  −
  AllowOverride None
  −
  order allow,deny
  −
  allow from all
  −
  AddType application/x-httpd-php .php
  −
  php_flag magic_quotes_gpc off
  −
  php_flag track_vars on
  −
  </Directory>
     −
expand-template /etc/httpd/conf/httpd.conf
+
[[User:Snoble|Snoble]] 01:59, 14 March 2010 (UTC)
   −
====php.ini====
+
I will mantain it for now, Paul Floor
   −
mkdir -p /etc/e-smith/templates-custom/etc/php.ini
+
=== Suggestions===
 +
If you can advise on standard configuration, please make it a bug so it is added to the rpm
   −
nano /etc/e-smith/templates-custom/etc/php.ini/99Zarafa
+
[[User:Snoble|Snoble]] 07:32, 22 December 2008 (UTC)
  extension = mapi.so
     −
expand-template /etc/php.ini
     −
Restart httpd
+
=== smeserver-zarafa-0.9-48===
   −
signal-event ibay-modify
+
/etc/e-smith/events/actions/zarafa-services-stop has been removed
   −
====.qmail====
+
/etc/e-smith/events/actions/zarafa-services
enable zarafa for a user
+
Usage: start|stop|restart|enabled|disabled
  db accounts setprop xxxx zarafa enabled
+
 +
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
   −
nano -w /etc/e-smith/templates-user/.qmail/80Zarafa
  −
  −
{
  −
    my $zarafa = $user->prop('zarafa') || 'disabled';
  −
  −
    return "| /usr/bin/zarafa-dagent -q $USERNAME"
  −
            if ($zarafa eq 'enabled');
  −
}
     −
/etc/e-smith/events/actions/qmail-update-user
+
InnoDB support is enabled automatically, we need to add this note later
   −
===Other tasks===
+
{{Note box| InnoDB support in MySql has been enabled in order to get zarafa-server running, for details see [[MySQL#Enable_InnoDB_engine]]}}
Change webaccess apache rights
     −
chown -R www:www /var/www/html/webaccess/tmp
+
=== zarafa-6.40 ===
   −
Start Zarafa services
+
yum localinstall libvmime-0*.rpm libical-0*.rpm zarafa-*.rpm catdoc-*.rpm
   −
/etc/init.d/zarafa-server start
+
==== indexing service ====
/etc/init.d/zarafa-spooler start
     −
Create Zarafa public store
+
The catdoc-rpm is needed for the new [http://www.zarafa.com/news/26-jan-zarafa-releases-community-version-its-collaboration-platform-640 indexing service] that is introduced with Zarafa 6.40... but the indexing-service is not yet handled by smeserver-zarafa. --[[User:Jester|jester]] 15:42, 13 February 2010 (UTC)
   −
/usr/bin/zarafa-admin -s
+
the catdoc rpm has un meet dependencies on SME 7 so it's only listed on discussion not the main page,
   −
===Usage===
+
yes it's not implemented yet, it'll only be implemented in sme8 unless others find the dependencies
After implementing the .qmail fragment mail is sent to zarafa, and NOT the users ~\Maildir
     −
====Webmail====
+
[[User:Snoble|Snoble]] 01:13, 20 February 2010 (UTC)
Access with browser for a local user
     −
* http://serverip/zarafa
+
Dependencies are poppler and poppler-utils.  Available here:
   −
====Windows Clients====
+
ftp://ftp.pbone.net/mirror/apt.kde-redhat.org/kde-redhat/redhat/4/i386/RPMS.stable/poppler-0.5.4-0.3.el4.i386.rpm
   −
* MS Outlook
+
ftp://ftp.pbone.net/mirror/apt.kde-redhat.org/kde-redhat/redhat/4/i386/RPMS.stable/poppler-utils-0.5.4-0.3.el4.i386.rpm
   −
* zarafaclient-*.msi contained in the win32 directory of zarafa-*.tar.gz
+
NOTE: Some poppler versions have been identified with security issues. I didn't have time to look into this version.
   −
====Imap & POP====
+
Paul Floor.
UNTESTED
     −
Start the service
+
=== SME 8 beta ===
/etc/init.d/zarafa-gateway start
     −
Configure the client (what address/port ?)
+
==== php 5.2.10 ====
   −
====Mobiles====
+
The php mapi files zarafa uses are compiled against 5.1.6, if sme 8 uses 5.2.10 we have a problem
UNTESTED
     −
Install rpm, start service, configure
+
here is one workaround http://forums.zarafa.com/viewtopic.php?f=9&t=3263&p=18753#p18753
   −
===Issues===
+
I found with the mapi error that I was getting was caused by my upgrade, PHP wouldn't start as the file libvmime.so.0 was missing or something rather (log no longer has the message). How I fixed my issue was I deleted the symlink in the /usr/lib/libvmime.so.0 which pointed to ...libvmime.0.7.1.so which is deleted when you upgrade the packages for version 7. I then "reinstalled" libvmime-0.9.2+... and restarted the httpd damaen and all was right with the world. -- girkers
   −
====Backup====
+
==== php 5.3 ====
*Either change the install location of the mail stores so they are backed up, requires using rpm -Uvh with a switch, not yum
+
If you update your system against the testing repo, it will update php to version 5.3 and thus break things again. To fix the mapi error this time, I uninstalled php-mapi that was included with zarafa (I was using 7.0.1.28479 that was included with zarafa) and this also removes the two dependencies of zarafa-webaccess and zarafa-webaccess-mobile (if they are installed). I then downloaded an updated php-mapi, installed it and then reinstalled the webaccess rpms and restarted the httpd and all good again. - Girkers
*Or document what directories to add to backups
     −
====.qmail fragment====
+
The steps I did were:
* mailsorting contrib sorts to Maildir folders, zarafa won't see this mail
+
cd /tmp
 +
wget ftp://ftp.pbone.net/mirror/download.fedora.redhat.com/pub/fedora/epel/5/i386/php53-mapi-7.0.1-1.el5.i386.rpm
 +
yum erase php-mapi
 +
yum localinstall php53-mapi-7.0.1-1.el5.i386.rpm
 +
cd zcp-[your version of zarafa]
 +
yum localinstall zarafa-webaccess-*
 +
sv t httpd-e-smith
5

edits

Navigation menu