Changes

Jump to navigation Jump to search
3,543 bytes removed ,  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 libical*.rpm zarafa-6*.rpm zarafa-webaccess-6*.rpm
+
=== Installation ===
   −
===Zarafa config files===
+
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).
   −
nano /etc/zarafa/server.cfg
+
Then install smeserver-zarafa. I could not retrieve this file from the smevdev repository (sme8 uses another one?).  
  mysql_user = zarafa
+
Get it manually and install:  
  mysql_password = 'yourpassword'
+
  wget http://ftp.nluug.nl/os/Linux/distr/smeserver/releases/7/smedev/i386/RPMS/smeserver-zarafa-0.9.0-53.el4.sme.noarch.rpm
  mysql_database = zarafa
+
  yum localinstall smeserver-zarafa-0.9.0-53.el4.sme.noarch.rpm
  −
  user_plugin        = unix
  −
  user_plugin_config = /etc/zarafa/unix.cfg
  −
 
  −
  attachment_storage      = files
  −
  attachment_path        = /home/e-smith/files/zarafa
  −
 
  −
+ mkdir /home/e-smith/files/zarafa
  −
 
  −
nano /etc/zarafa/unix.cfg
  −
  default_domain = yourserver.net
  −
  min_user_uid = 5000
  −
  min_group_gid = 5000
  −
 
  −
: I think that due to issues that arise from the unix plugin (including but not limited to) failed Outlook and Multi-Company support, we should revert back to using the db plugin.
  −
:: go for it, So for a new user, 1. create in SME, 2. set qmail prop, 3. create in zarafa ?
  −
:: if this is the way to go we tie zarafa commands into user-[create-delete], conf-password? etc
  −
:: How hard is the transition, do you need to drop database/start again ?
  −
 
  −
===SME templates===
  −
 
  −
====httpd.conf====
  −
 
  −
  mkdir -p /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf
  −
 
  −
nano /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf/86ZarafaAlias
  −
  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
     −
consider 'adding' a generic alias, just add a line below the other Alias
+
/etc/e-smith/events/actions/zarafa-install
  Alias /webaccess /var/www/html/webaccess/
     −
====php.ini====
+
expand the php-mapi patch patch and and the symbolic links (see first text block above: Zarafa7 on SME8).
   −
mkdir -p /etc/e-smith/templates-custom/etc/php.ini
+
If you use webaccess mobile, change 86ZarafaAlias template [[bugzilla:6552]]
   −
  nano /etc/e-smith/templates-custom/etc/php.ini/99Zarafa
+
If you use z-push, download and install (see [[Zarafa | here]] mobile synchronization).
  extension = mapi.so
+
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
   −
expand-template /etc/php.ini
+
Then post-upgrade and restart.  
   −
Restart httpd
+
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.  
signal-event ibay-modify
  −
 
  −
====.qmail====
  −
enable zarafa for a user
  −
  db accounts setprop xxxx zarafa enabled
  −
 
  −
mkdir -p /etc/e-smith/templates-user-custom/.qmail
  −
nano -w /etc/e-smith/templates-user-custom/.qmail/80Zarafa
   
   
 
   
  {
+
  yum install MySQL-python
    my $zarafa = $user->prop('zarafa') || 'disabled';
  −
  −
    return "| /usr/bin/zarafa-dagent -q $USERNAME ; if [ $? -ne 0 ] ; then exit -1; else exit 99; fi;"
  −
            if ($zarafa eq 'enabled');
  −
}
     −
  /etc/e-smith/events/actions/qmail-update-user
+
  python /usr/share/doc/zarafa/zarafa7-upgrade
   −
===Create the Database===
+
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]]).  
mysqladmin create zarafa
  −
mysql -e "grant all privileges on zarafa.* to zarafa@localhost identified by 'yourpassword'"
  −
  mysql -e "flush privileges"
     −
===Other tasks===
+
===Sogo===
Change webaccess apache rights
     −
chown -R www:www /var/www/html/webaccess/tmp
+
FYI, I'm now using [[Sogo]] instead of zarafa, hence I have stopped work on smeserver-zarafa.
   −
Configure Zarafa services and add links for auto start
+
Sogo may not be as complete as zarafa, but is simpler to intergrate/maintain and will likely have a wider usage.
   −
config set zarafa-server service status enabled
+
[[User:Snoble|Snoble]] 01:59, 14 March 2010 (UTC)
config set zarafa-spooler service status enabled
  −
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99zarafa-server
  −
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99zarafa-spooler
     −
Configure Zarafa calendar scheduling. (http://en.wikipedia.org/wiki/TNEF)
+
I will mantain it for now, Paul Floor
   −
config setprop smtpd tnef2mime disabled
+
=== Suggestions===
signal-event email-update
+
If you can advise on standard configuration, please make it a bug so it is added to the rpm
   −
Start Zarafa services
+
[[User:Snoble|Snoble]] 07:32, 22 December 2008 (UTC)
   −
/etc/init.d/zarafa-server start
  −
/etc/init.d/zarafa-spooler start
     −
Create Zarafa public store
+
=== smeserver-zarafa-0.9-48===
   −
/usr/bin/zarafa-admin -s
+
/etc/e-smith/events/actions/zarafa-services-stop has been removed
   −
Assigning an administrator
+
  /etc/e-smith/events/actions/zarafa-services
 
+
Usage: start|stop|restart|enabled|disabled
When a user is an administrator, the user will be allowed to open all Zarafa stores of any user.
+
 
+
  start services
List users:
+
  stop services
  /usr/bin/zarafa-admin -l
+
  restart services
 
+
  enabled - set db values to enabled, zarafa will start on reboot
Update a user to admin status:
+
  disabled - set db values to disabled, zarafa won't start on reboot
/usr/bin/zarafa-admin -u <username> -a 1
  −
 
  −
===Usage===
  −
After implementing the .qmail fragment mail is sent to zarafa, and NOT the users ~\Maildir
  −
 
  −
====Webmail====
  −
Access with browser for a local user
  −
 
  −
http://server/zarafa
  −
 
  −
====Outlook====
  −
To use MS Outlook
  −
 
  −
Configure, enable and start /etc/init.d/zarafa-licensed
  −
 
  −
Install the zarafaclient-*.msi add-on contained in the win32 directory of zarafa-*.tar.gz
  −
 
  −
=====Zarafa-client & Outlook 2007 0x80040700=====
  −
Appears to be an issue when the user_plugin=unix finds matching user/group names (SME design):
  −
 
  −
http://forums.zarafa.com/viewtopic.php?f=12&t=1083
  −
 
  −
=====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
  −
 
  −
  nano /etc/zarafa/gateway.cfg
  −
  pop3_enable    =      no
  −
  pop3s_enable    =      no
  −
  imap_enable    =      yes
  −
  imap_port      =      144
  −
  imaps_enable    =      no
  −
 
  −
  config set zarafa-gateway service TCPPort 144 access private status enabled [access public/private as required]
  −
  ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99zarafa-gateway
  −
/etc/init.d/zarafa-gateway start; signal-event remoteaccess-update
  −
 
  −
Configure your IMAP client to use port 144
  −
 
  −
====Calendar====
  −
http://download.zarafa.com/zarafa/release/docs/zarafa_ical_gateway.en.pdf
     −
To access the calendar functions with an iCal client eg, Thunderbird and Lighting
  −
  −
nano /etc/zarafa/ical.cfg [maybe use icals on 8443]
  −
  ical_enable = yes
  −
  ical_port = 8088
  −
  −
config set zarafa-ical service TCPPort 8088 access private status enabled [access public/private as required]
  −
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S99zarafa-ical
  −
/etc/init.d/zarafa-ical start; signal-event remoteaccess-update
  −
  −
in Tbird/Lightning > New Calendar > on network > ical > http://<domain>:8088/ical/<user>/calendar/
  −
  −
Note, there are problems with reading events created with /webaccess http://forums.zarafa.com/viewtopic.php?f=13&t=1019
  −
  −
====Mobiles====
  −
To sync the data in zarafa to a compatible device
  −
  −
Install rpm, start service, configure
  −
  −
===Issues===
  −
  −
====Backup====
  −
Nothing to do, data is in mysql, config files are in /etc/zarafa, attachments in /home/e-smith/files/zarafa
  −
  −
====Store_attachment_outside_of_the_database====
  −
Early wiki instructions stored attachments in mysql, if you just edit the config file zarafa may fail to start.
  −
One way to fix is by dropping the database (this deletes your data), and recreating the database with the server.cfg setting set to files.
  −
  −
====.qmail fragment====
  −
* mailsorting contrib sorts to Maildir folders, zarafa won't see this mail. Disable procmail/maildrop and re-create internal zarafa rules
  −
  −
====sv sigusr1 httpd-e-smith====
  −
Eg. modifying an ibay, causes a problem with webaccess
  −
  −
tail /var/log/messages
  −
<snip>
  −
Sep 28 16:30:27 kiwi httpd: PHP Warning:  Function registration failed - duplicate name - mapi_zarafa_getuser in Unknown on line 0
  −
Sep 28 16:30:27 kiwi httpd: PHP Warning:  Function registration failed - duplicate name - mapi_zarafa_getgroup in Unknown on line 0
  −
Sep 28 16:30:27 kiwi httpd: PHP Warning:  mapi:  Unable to register functions, unable to load in Unknown on line 0
  −
  −
most of these events will cause webaccess to break
  −
# ls -la `slocate services2adjust | grep httpd-e-smith`
  −
/etc/e-smith/events/console-save/services2adjust/httpd-e-smith -> restart
  −
/etc/e-smith/events/domain-create/services2adjust/httpd-e-smith -> sigusr1
  −
/etc/e-smith/events/domain-delete/services2adjust/httpd-e-smith -> sigusr1
  −
/etc/e-smith/events/domain-modify/services2adjust/httpd-e-smith -> sigusr1
  −
/etc/e-smith/events/email-update/services2adjust/httpd-e-smith -> sigusr1
  −
/etc/e-smith/events/host-create/services2adjust/httpd-e-smith -> sigusr1
  −
/etc/e-smith/events/host-delete/services2adjust/httpd-e-smith -> sigusr1
  −
/etc/e-smith/events/host-modify/services2adjust/httpd-e-smith -> sigusr1
  −
/etc/e-smith/events/ibay-create/services2adjust/httpd-e-smith -> sigusr1
  −
/etc/e-smith/events/ibay-delete/services2adjust/httpd-e-smith -> sigusr1
  −
/etc/e-smith/events/ibay-modify-servers/services2adjust/httpd-e-smith -> sigusr1
  −
/etc/e-smith/events/ibay-modify/services2adjust/httpd-e-smith -> sigusr1
  −
/etc/e-smith/events/ldap-update/services2adjust/httpd-e-smith -> sigusr1
  −
/etc/e-smith/events/logrotate/services2adjust/httpd-e-smith -> sigusr1
  −
/etc/e-smith/events/network-create/services2adjust/httpd-e-smith -> sigusr1
  −
/etc/e-smith/events/network-delete/services2adjust/httpd-e-smith -> sigusr1
  −
/etc/e-smith/events/remoteaccess-update/services2adjust/httpd-e-smith -> sigusr1
  −
/etc/e-smith/events/timezone-update/services2adjust/httpd-e-smith -> restart
     −
workaround is to
+
InnoDB support is enabled automatically, we need to add this note later
sv restart httpd-e-smith
     −
fix is to work out why php is giving an error
+
{{Note box| InnoDB support in MySql has been enabled in order to get zarafa-server running, for details see [[MySQL#Enable_InnoDB_engine]]}}
   −
====Address book====
+
=== zarafa-6.40 ===
The Zarafa global address book finds users and groups from /etc/passwd etc/group
     −
We don't want machine names, ibays, system, the group of a user, maybe others.  
+
yum localinstall libvmime-0*.rpm libical-0*.rpm zarafa-*.rpm catdoc-*.rpm
I don't see how to hide them, changing shell to /bin/false may break things
     −
====Folder Naming====
+
==== indexing service ====
SME and Zarafa use different folder naming. To enhance migration SME folders should be renamed prior to migration.
     −
drafts > Drafts
+
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)
junkmail > Junk E-mail
  −
sent-mail > Sent Items
  −
trash > Deleted Items
     −
====Migrating users and data to Zarafa====
+
the catdoc rpm has un meet dependencies on SME 7 so it's only listed on discussion not the main page,
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
+
yes it's not implemented yet, it'll only be implemented in sme8 unless others find the dependencies
   −
=====IMAP migration from SME/IMAP to Zarafa/IMAP=====
+
[[User:Snoble|Snoble]] 01:13, 20 February 2010 (UTC)
   −
Configure zarafa-gateway for migration enabling IMAP on port 144 only as shown above
+
Dependencies are poppler and poppler-utils.  Available here:
   −
Get imapsync and required perl module
+
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
   −
wget http://dag.wieers.com/rpm/packages/perl-Mail-IMAPClient/perl-Mail-IMAPClient-2.2.9-1.2.el4.rf.noarch.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
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
+
NOTE: Some poppler versions have been identified with security issuesI didn't have time to look into this version.
  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)
+
Paul Floor.
   −
imapsync --noauthmd5 --host1 localhost --port1 143 --user1 <username> --password1 <password> --sep2 / --prefix2 "" --host2 localhost --port2 144 --user2 <username> --password2 <password>
+
=== SME 8 beta ===
   −
Example to synchronize a user named 'bob' with password 'bob123' from SME IMAP into Zarafa:
+
==== php 5.2.10 ====
   −
imapsync --noauthmd5 --host1 localhost --port1 143 --user1 bob --password1 bob123 --sep2 / --prefix2 "" --host2 localhost --port2 144 --user2 bob --password2 bob123
+
The php mapi files zarafa uses are compiled against 5.1.6, if sme 8 uses 5.2.10 we have a problem
   −
After syncing is complete, stop zarafa-gateway service and/or edit /etc/zarafa/gateway.cfg to meet your needs.
+
here is one workaround http://forums.zarafa.com/viewtopic.php?f=9&t=3263&p=18753#p18753
   −
===SME Actions===
+
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
Actions to be linked into events
     −
====user-delete====
+
==== php 5.3 ====
To delete a user from the server, use the following command:
+
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
  /usr/bin/zarafa-admin -d <user name>
  −
The user will be deleted from the database. The store of the user will be placed in the
  −
public store, in a 'Deleted Stores' folder. This folder is only available to administrative
  −
users of Zarafa.
     −
=== Bugs ===
+
The steps I did were:
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}}.
+
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