Difference between revisions of "Talk:Zarafa"

From SME Server
Jump to navigationJump to search
m (Added information on updating php-mapi if upgraded php to version 5.3)
 
(53 intermediate revisions by 8 users not shown)
Line 1: Line 1:
−
===Feedback===
+
=== Zarafa7 on SME8 ===
 +
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
  
−
I uninstalled my original Zarafa setup and re-installed using the smeserver RPM Darrell created - all worked fine. I also migrated some email that I'd created in the test accounts for that purpose. This also went well. I happened to have one account in Thunderbird - the test email in the Inbox showed unread when I went into the account. However, the other account, accessed via the Zarafa web interface, showed the Inbox message as read.
+
=== Dependancies ===
  
−
Overall, the smeserver alpha RPM works well. Many thanks for it, Darrell.
+
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
  
−
===Bugs===
+
If you are upgrading from version 6 you will also need these dependencies:
−
[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=&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&field0-0-0=noop&type0-0-0=noop&value0-0-0=Open Search all bugs] for smeserver-zarafa at bugs.contribs.org for history
+
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
  
 +
- Garth Kirkwood (girkers)
  
−
===Mobile synchronisation===
+
=== Installation ===
  
−
{{Warning box|I DON'T KNOW WHAT I'M DOING!!
+
To make things a bit more easy for non Zarafa experts, I used this procedure for a clean install.
−
PLEASE CHECK THE CODE FOR ERRORS AND SECURITY ISSUES!!
+
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).
  
−
HAVE NOT FIGURED OUT HOW TO -ONLY- USE SSL YET!!}}
+
Then install smeserver-zarafa. I could not retrieve this file from the smevdev repository (sme8 uses another one?).
 +
Get it manually and install:
 +
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
  
 +
/etc/e-smith/events/actions/zarafa-install
  
−
To enable synchronization of your mobile phone through ActiveSync with Zarafa, Z-push needs to be installed.
+
expand the php-mapi patch patch and and the symbolic links (see first text block above: Zarafa7 on SME8).
  
−
You can find the original Z-push installation documentation here: http://download.zarafa.com/zarafa/release/docs/z-push_installation_manual.en.pdf
+
If you use webaccess mobile, change 86ZarafaAlias template [[bugzilla:6552]]
  
 +
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
  
−
Download the latest Z-push version (see: http://z-push.sourceforge.net).
+
Then post-upgrade and restart.  
−
# wget http://download2.berlios.de/z-push/z-push-1.2.tar.gz
 
  
−
Extract the files:
+
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]]!
−
  # tar -zxvf z-push-1.2.tar.gz -C /var/www/html
+
Stop running zarafa services, make sure a backup of the zarafa mysql database exists, install MySQL-python, run update script.
 +
 +
yum install MySQL-python
  
−
'State'-dir needs to be writable for apache:
+
  python /usr/share/doc/zarafa/zarafa7-upgrade
−
  # cd /var/www/html/z-push/
 
−
# chmod 755 state
 
−
# chown www:www state
 
  
−
Make a new template fragment:
+
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]]).
−
# mkdir -p /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/
 
−
# pico /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/86Z-PushAlias
 
  
−
Edit the fragment and add:
+
===Sogo===
−
Alias /Microsoft-Server-ActiveSync /var/www/html/z-push/index.php
 
−
<Directory /var/www/html/z-push/>
 
−
    Options -Indexes
 
−
    AllowOverride None
 
−
    order allow,deny
 
−
    allow from all
 
−
    AddType application/x-httpd-php .php
 
−
    php_flag magic_quotes_gpc off
 
−
    php_flag register_globals off
 
−
    php_flag magic_quotes_runtime off
 
−
    php_flag short_open_tag on
 
−
</Directory>
 
  
−
Expand the template:
+
FYI, I'm now using [[Sogo]] instead of zarafa, hence I have stopped work on smeserver-zarafa.
−
# expand-template /etc/httpd/conf/httpd.conf
 
  
−
Restart httpd (the currently for Zarafa only save way):
+
Sogo may not be as complete as zarafa, but is simpler to intergrate/maintain and will likely have a wider usage.
−
# sv restart httpd-e-smith
 
  
−
====Synchronise using SSL====
+
[[User:Snoble|Snoble]] 01:59, 14 March 2010 (UTC)
−
{{Incomplete}}
 
  
 +
I will mantain it for now, Paul Floor
  
−
====Know working hardware====
+
=== Suggestions===
−
Tested and working with WinMobile 6.1 on a HTC TyTN II over a NON SSL connection (mail-push not yet tested).
+
If you can advise on standard configuration, please make it a bug so it is added to the rpm
  
−
===Additional Notes===
+
[[User:Snoble|Snoble]] 07:32, 22 December 2008 (UTC)
−
Darrell, I have installed Zarafa manually using custom-templates/db settings and have most everything working flawlessly including the Outlook plugin, and z-push to a WM6 device and I am EXTREMELY impressed.  I have a desktop, laptop and my Samsung i760 in perfect sync.  The z-push actually "pushes" and emails, calendar, contact changes happen almost instantaneously.
 
  
−
I have a couple of pointers if you are still working on this project.
 
  
−
I notice you use the "db" setting for your users.  I found the unix plugin a superb tool.  It automatically adds all system users and keeps them in sync including password changes and user additions/deletions.  It works on the fly.  The only drawback is the fact SME uses weird user/group numbering so you have to include users from 5000 up and then exclude all groups by configuring uniz.cfg to a high range like 10001-10001.  I also did not include admin as one of the users due to the limitations on how the unix plugin handles users/groups.
+
=== smeserver-zarafa-0.9-48===
  
−
1- I also placed a rewrite rule to force https.
+
/etc/e-smith/events/actions/zarafa-services-stop has been removed
−
RewriteRule ^/Microsoft-Server-ActiveSync(/.*|$)    https://%{HTTP_HOST}/Microsoft-Server-ActiveSync$1 [L,R]
 
  
−
2- You can sort junk email to zarafa and have it automatically placed in the Junk E-mail folder. This works in the .qmail-junkmail template. Note the -qj switch. This tells zarafa-dagent to place the email in the Junk E-mail folder.
+
/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
  
−
http://bugs.contribs.org/show_bug.cgi?id=4705
 
  
−
Some other notes:
+
InnoDB support is enabled automatically, we need to add this note later
−
I totally disabled horde (no big loss there) and pop and imap and my implementation either uses horde OR zarafa but not both.  I run zarafa on the standard ports and transitioned 15 users last night.  Some using Outlook (pop) and they didn't notice anything.  A few use webmail and I left the alias alone and those users all logged in this morning to a big surprise and they were all extremely happy.
 
  
−
For this to work, you need to configure zarafa to use the certs already generated in SME.  Hope this helps.
+
{{Note box| InnoDB support in MySql has been enabled in order to get zarafa-server running, for details see [[MySQL#Enable_InnoDB_engine]]}}
  
−
Paul
+
=== zarafa-6.40 ===
  
−
  Hi Paul, please submit separate bug reports detailing all your customization notes. Darrell
+
  yum localinstall libvmime-0*.rpm libical-0*.rpm zarafa-*.rpm catdoc-*.rpm
  
−
=== SSL ===
+
==== indexing service ====
  
−
I've been trying to get SSL working for both IMAP and the Outlook configuration. For IMAP, I edited the gateway.cfg template to point to the SME Server certificate and key files:
+
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)
  
−
File with RSA key for SSL:
+
the catdoc rpm has un meet dependencies on SME 7 so it's only listed on discussion not the main page,
  
−
ssl_private_key_file    =      /home/e-smith/ssl.key/host.domain.com.key
+
yes it's not implemented yet, it'll only be implemented in sme8 unless others find the dependencies
  
−
File with certificate for SSL:
+
[[User:Snoble|Snoble]] 01:13, 20 February 2010 (UTC)
  
−
ssl_certificate_file    =      /home/e-smith/ssl.crt/host.domain.com.crt
+
Dependencies are poppler and poppler-utils. Available here:
  
−
On restart of the daemon, I was successfully able to connect. In looking further at the Outlook side, SSL support for the server is configured in server.cfg, where it requires a path to CA certificates. Using the steps outlined in the zarafa-server man page, I created a CA and certificate which I then specified in server.cfg. I was then able to configure the Outlook profile to use port 237 and connect successfully.
+
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
  
−
N.B. There is a typo in the man page - the shell script should be /usr/share/zarafa/ssl-certificates.sh - the man page is missing the "s" in certificates.
+
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
  
−
NOTE: There is no need to create any additional certificates, the SME self signed certificates work just fine for Outlook SSL connections.  In server.cfg in the SSL section (on or about line 104) you need to point to the correct certs and paths like this:
+
NOTE: Some poppler versions have been identified with security issues.  I didn't have time to look into this version.
  
−
server_ssl_key_file    = /home/e-smith/ssl.pem/host.domain.com.pem
+
Paul Floor.
  
−
server_ssl_ca_file      = /home/e-smith/ssl.crt/host.domain.com.crt
+
=== SME 8 beta ===
  
−
server_ssl_ca_path      = /home/e-smith/ssl.crt/
+
==== php 5.2.10 ====
  
−
sslkeys_path            = /home/e-smith/ssl.pem/
+
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
 +
 
 +
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
 +
 
 +
==== php 5.3 ====
 +
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
 +
 
 +
The steps I did were:
 +
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

Latest revision as of 07:26, 4 October 2011

Zarafa7 on SME8

If you want to test the new Zarafa 7 version on SME8b6: install as described 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

Dependancies

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

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

- Garth Kirkwood (girkers)

Installation

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).

Then install smeserver-zarafa. I could not retrieve this file from the smevdev repository (sme8 uses another one?). Get it manually and install: 

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

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

expand the php-mapi patch patch and and the symbolic links (see first text block above: Zarafa7 on SME8).

If you use webaccess mobile, change 86ZarafaAlias template bugzilla:6552

If you use z-push, download and install (see 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 [zarafa administration manual]! Stop running zarafa services, make sure a backup of the zarafa mysql database exists, install MySQL-python, run update script. 

yum install MySQL-python

python /usr/share/doc/zarafa/zarafa7-upgrade

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 [zarafa administration manual]).

Sogo

FYI, I'm now using Sogo instead of zarafa, hence I have stopped work on smeserver-zarafa.

Sogo may not be as complete as zarafa, but is simpler to intergrate/maintain and will likely have a wider usage.

Snoble 01:59, 14 March 2010 (UTC)

I will mantain it for now, Paul Floor

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, we need to add this note later


Important.png Note:
InnoDB support in MySql has been enabled in order to get zarafa-server running, for details see MySQL#Enable_InnoDB_engine


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,

yes it's not implemented yet, it'll only be implemented in sme8 unless others find the dependencies

Snoble 01:13, 20 February 2010 (UTC)

Dependencies are poppler and poppler-utils. Available here:

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

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

NOTE: Some poppler versions have been identified with security issues. I didn't have time to look into this version.

Paul Floor.

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

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

php 5.3

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

The steps I did were: 

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
Retrieved from "https://wiki.koozali.org/index.php?title=Talk:Zarafa&oldid=15895"