Active Sync with Zarafa and Z-push, Setup

Update 2015-06-15:
Because Zarafa Z-push does not work reliable, I use now Baikal, 2014-06-26 for Android contacts and calendar synch. Also the synch to Mac OS X Yosemite does work now reliable.

In order to sync Android contacts and calendar to a server database at home, a Linux server can be used. I will describe an installation on Ubuntu 12.04.

The method was described in the German computer magazine c't 15-2011, page 134-139, and Linux kompakt 01/12, page 68-75 (www.heise.de).

Unfortunately a Contacts sync to Mac OS X could not be done with Zarafa. But there is an extra backend sabre-zarafa which can do the job, please see ActiveSyncZarafa/SabreZarafa.

For a better understanding of the data flow, please see a diagram in AndroidSyncPrivate#Data_Flow .

A new groupware solution is coming 2012 from http://owncloud.org version 4. Lets see, if it is better. A test in September 2012 shows, that a vCard file from a Mac with 209 contacts could import 153 contacts only. Also the Mac OS client could not be started under Mountain Lion 10.8.1. So, it is not yet usable, see details in AndroidOwncloud.

Zarafa plus SSL Ubuntu 12.04, zcp 7.1.4

Download from http://download.zarafa.com the latest release (e.g. zcp-7.1.4-41394-ubuntu-12.04-i386-free.tar.gz, 44.5 MB, 2013-03-28) for Ubuntu 12.04.

Install (Update) and configurate Zarafa with the following commands:

# move package
$ mv Downloads/zcp-7.1.4-41394-ubuntu-12.04-i386-free.tar.gz Install/Zarafa

$ cd Install/Zarafa
# unpack the packages
$ tar xzf zcp-7.1.4-41394-ubuntu-12.04-i386-free.tar.gz

# Install
$ cd zcp-7.1.4-41394-ubuntu-12.04-i386/
$ sudo ./install.sh
  Zarafa Collaboration Platform, version zcp-7.1.4-41394
  ...
  About to install for Ubuntu 12.04 i386
  Found MySQL version 5.5

  We will now install Zarafa onto your system. You may be
  required to install dependencies if the installation fails.
  Press <enter> to continue
  ...
  Webaccess files have been moved to /usr/share/zarafa-webaccess
  Please read /usr/share/doc/zarafa-webaccess/NEWS.Debian.gz for more information
  ....
  Installation of the software is complete.
  We will now configure Zarafa services.

  Please answer the following questions:
  Serial number must be 25 characters or empty
  Server serial number (leave empty for none) [] :
  The correctness of the serial will be checked when the server starts.

  MySQL Server [localhost]  :
  MySQL Port [3306]         :
  MySQL User [root]         :
  MySQL Password []         : [password]
  Database name [zarafa]    :
  Log method (file or syslog) [file]  :
  Log filename [/var/log/zarafa/server.log]  :

  Creating spooler configuration ...
  The spooler program sends outgoing e-mail using an SMTP server
  Please answer the following questions:
  SMTP server [localhost]  :
  Log method (file or syslog) [file]  :
  Log filename [/var/log/zarafa/spooler.log] :

  Creating monitor configuration ...
  The monitor program sends quotas warning mails to users who are over quota.
  Please answer the following questions:
  Warning e-mail resend interval (in days) [1]  :
  Log method (file or syslog) [file]  :
  Log filename [/var/log/zarafa/monitor.log] :

  Do you wish to run Zarafa gateway (POP3/IMAP)
   services as wll? [y]   :
  Log method (file or syslog) [file]  :
  Log filename [/var/log/zarafa/gateway.log] :
  POP3 port [110]  :
  **Warning: When another service is currently providing POP3 support,
             the gateway may not start because the port is already in use.
  IMAP port [143]  :
  **Warning: When another service is currently providing IMAP support,
             the gateway may not start because the port is already in use.

  Do you wish to run Zarafa Ical gateway (iCal/CalDAV)
   services as well? [y]

  Do you wish to run Zarafa indexer service? [y]
  Already installed, skipping services.

  Done configuration services
  Press <enter> to continue ...

  The server is running on port 236

  If you wish to make changes, please edit the file /etc/zarafa/server.cfg
  or /etc/zarafa/license/base for the serial number.

  If you wish to make changes to the spooler or monitor configuration
  please edit the file spooler.cfg or monitor.cfg in the directory
  /etc/zarafa/.

  To start Zarafa, you must run
  /etc/init.d/zarafa-server start
  Do you wish to start the server now [y]  :
   * Stopping Zarafa server: zarafa-server
  No /usr/bin/zarafa-server found running; none killed
   * Starting Zarafa server: zarafa-server        [OK]

  We will now create the public store with the 'zarafa-admin -s' command
  Public created

  Use the 'zarafa-admin -c' comand to create users.
  Read the help or manual page for details, by typing:
  man zarafa-admin

  Press <enter> to continue ...

  To start the dagent, spooler, monitor and gateway services, you must run
  /etc/init.d/zarafa-dagent start
  /etc/init.d/zarafa-spooler start
  /etc/init.d/zarafa-monitor start
  /etc/init.d/zarafa-gateway start
  /etc/init.d/zarafa-ical start

  Do you wish to start the configured services now? [y]  :
  ...
   * Starting Zarafa LMTP dagent: zarafa-dagent [ OK ]
  ...
   * Starting Zarafa spooler: zarafa-spooler   [OK]
  ...
   * Starting Zarafa monitor: zarafa-monitor   [OK]
  Warning: Terminal locale not UTF-8, but UTF-8 locale is beeing forced.
           Screen output may not be correctly printed.

  Press <enter> to continue ...
  ...
   * Starting Zarafa gateway: zarafa-gateway   [OK]
  ...
   * Starting Zarafa indexer: zarafa-indexer   [OK]
  ...
   * Starting Zarafa licensed: zarafa-licensed   [OK]
  Press <enter> to continue ...

  Currently the server is configured to accept SOAP connections on port
  236. If you wish to connect Outlook clients on port 80,
  please setup your web server to proxy HTTP requests with
  URI=/zarafa to 236. This can be done in Apache2 with mod_proxy
  with the ProxyPass configuration directive:

  ProxyPass        /zarafa http://localhost:236
  ProxyPassReverse /zarafa http://localhost:236

  The modules 'proxy' and 'proxy_http' need to be enabled.

  Enter 'a2enmod proxy' to enable the mod_proxy module.
  Do not forget to reload apache when you have altered the configuration.

  The web access may already be available from http://server/webaccess
  The new WebApp may already be available from http://server/webapp.

# The hostname must be set in accordance to the domain name
# /etc/hostname = rudiswiki.de
# /etc/hosts
  127.0.0.1  rudiswiki.de 
  127.0.0.1  localhost.localdomain localhost 

# add SSL for Apache2 with Ubuntu certificate
$ sudo a2enmod ssl
$ sudo a2ensite default-ssl
# Edit /etc/apache2/sites-available/default-ssl if neccesary

$ sudo service apache2 reload

# Allow in the router port forwarding 443, if Internet SSL access is wanted.

# This time a self generated certificate is used (Z-push installation manual):
$ sudo sh
$ cd /root
$ mkdir ssl
$ cd ssl
# To create a self signed certificate you first need to setup your own CA by the following commands:
$ openssl genrsa -des3 -out ca.key 4096
Generating RSA private key, 4096 bit long modulus
...
e is 65537 (0x10001)
Enter pass phrase for ca.key:
Verifying - Enter pass phrase for ca.key:

$ openssl req -new -x509 -days 3650 -key ca.key -out ca.crt
Enter pass phrase for ca.key:
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [AU]:DE
State or Province Name (full name) [Some-State]:.
Locality Name (eg, city) []:Wiesbaden
Organization Name (eg, company) [Internet Widgits Pty Ltd]:RudolfReuter
Organizational Unit Name (eg, section) []:.
Common Name (e.g. server FQDN or YOUR name) []:www.rudiswiki.de
Email Address []:reuterr@web.de

# After your CA is ready, you need to create a Certificate Signing Requests (CSR).
$ openssl genrsa -out rudiswiki.key 1024
Generating RSA private key, 1024 bit long modulus
.................++++++
....................++++++
e is 65537 (0x10001)
$ chmod 400 rudiswiki.key

$ openssl req -new -nodes -key rudiswiki.key -out rudiswiki.csr
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [AU]:DE
State or Province Name (full name) [Some-State]:.
Locality Name (eg, city) []:Wiesbaden
Organization Name (eg, company) [Internet Widgits Pty Ltd]:RudolfReuter
Organizational Unit Name (eg, section) []:.
Common Name (e.g. server FQDN or YOUR name) []:www.rudiswiki.de
Email Address []:reuterr@web.de

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:.
An optional company name []:.

$ openssl x509 -req -days 3650 -in rudiswiki.csr -CA ca.crt -CAkey ca.key -set_serial 01 -out rudiswiki.crt
Getting CA Private Key
Enter pass phrase for ca.key:

$ cp rudiswiki.crt /etc/ssl/certs/rudiswiki.crt
$ cp rudiswiki.key /etc/ssl/private/rudiswiki.key

$ exit  # exit root shell

# In order to allow iCal SSL access, edit /etc/zarafa/ical.cfg
# 2012-09-15 because of a problem with self signed certificate, use old one from /Bilder/rudiswiki/SSL
# change no to yes
  icals_enable = yes
# check for 8443
  icals_port = 8443
# File with RSA key for SSL
  ssl_private_key_file = /etc/ssl/private/ssl-cert-snakeoil.key
or trusted SSL
  ssl_private_key_file = /etc/ssl/private/rudiswiki.de.key

#File with certificate for SSL
  ssl_certificate_file = /etc/ssl/certs/ssl-cert-snakeoil.pem
or trusted SSL
  ssl_certificate_file = /etc/ssl/certs/rudiswiki.de.crt

# update daemon
$ sudo /etc/init.d/zarafa-ical restart

# test if it works
$ nmap localhost
...
8080/tcp open  http-proxy
8443/tcp open  https-alt   # OK

# check fritz.box, Internet/Freigaben
  HTTPS-Server CalDAV   TCP     8443    rudiswiki       8443

# web browser address test:
# you have to acknowledge that if it is a non trusted certificate.
https://www.rudiswiki.de:8443/caldav  # a login mask appears, for calendar - OK

# In order to allow iCal SSL access, edit /etc/zarafa/gateway.cfg
# File with RSA key for SSL
ssl_private_key_file    =       /etc/ssl/private/ssl-cert-snakeoil.key
or trusted SSL
ssl_private_key_file = /etc/ssl/private/rudiswiki.de.key

#File with certificate for SSL
ssl_certificate_file    =       /etc/ssl/certs/ssl-cert-snakeoil.pem
or trusted SSL
ssl_certificate_file = /etc/ssl/certs/rudiswiki.de.crt

# update daemon
$ sudo /etc/init.d/zarafa-gateway restart

REMARK: Unfortunately the self made certificate rudiswiki.crt does not work, 
        so use the certificate rudiswiki.de.crt.

# To backup the MySQL database (25 MB)
$ cd Install/zarafa
$ sudo mysqldump --single-transaction -p[password] zarafa > dumpDB_zarafa-201207181505.sql

# Restore database, including user data
$ cd Install/zarafa
$ sudo ./restoreDB_zarafa.sh

# change locale to German
$ sudo gedit /etc/default/zarafa
# exchange 'ZARAFA_LOCALE="C"' to 'ZARAFA_LOCALE="de_DE.UTF-8"'
# exchange 'ZARAFA_USERSCRIPT_LOCALE="C"' to 'ZARAFA_USERSCRIPT_LOCALE="de_DE.UTF-8"'
# save to file and exit gedit
$ sudo /etc/init.d/zarafa-server restart
   * Starting Zarafa server: zarafa-server        [OK]

$ sudo /usr/bin/zarafa-admin -c reuterru -p [password] -e reuterru@googlemail.com -f 'Rudolf Reuter'
  User created
$ sudo /usr/bin/zarafa-admin -c reuter.ingeb -p [password] -e reuter.ingeb@googlemail.com -f 'Ingeborg Reuter'
  User created

# In case of a wrong typing you can delete the user with:
$ sudo /usr/bin/zarafa-admin -d reuterru

# ATTENTION: deleting users will create orphan stores. In order to delete them use a shell script:
  http://www.zarafa.com/wiki/index.php/Permanently_delete_all_orphan_stores
  I named it zarafa_del_orphans.sh in /home/rudi/Install/zarafa
$ sudo bash ./zarafa_del_orphans.sh
  If you run it without "bash" you might get an error: [: y: unexpected operator, see link.

# update Apache2
$ sudo /etc/init.d/apache2 reload

# Each calendar event is a single xxx.ics file.
  /Users/rudi/Library/Calendars/78...caldav/0C...calendar/Events/0A...ics
# For Import in Zarafa calendar, copy all *.ics files lokal to the server.
# Install curl
$ sudo apt-get install curl
$ Import ics events from folder "Events"
  0A6A2093-DE52-4E7F-BB12-7B420FFFAB32.ics 2012-09-15
$ curl -u reuterru:ozasol1011 -T /home/rudi/Install/Zarafa/Calendar/Events/0A... http://localhost:8080/ical/reuterru

# Import all events from a local folder.
# use "-exec echo $(date) {} \; | tee ics.log" in order to see the single events.
$ cd /home/rudi/Install/Zarafa/Calendar
$ find Events -name '*.ics' -exec curl -u reuterru:[password] -T {} http://localhost:8080/ical/reuterru \; -exec echo $(date) {} \; | tee ics.log; echo $(date)

# with "wc -l ics.log" you can see the number of transferred events.
$ wc -l ics.log
  2522 ics.log # but in Zarafa calendar 296 objects only

The time to import 2522 local x.ics files in the Zarafa data base took 64 minutes, remembers me to the time of C64 :-(

After the import, no calendar events show up, but you can find them in the Restore Deleted Items list. So with the function Restore All you can bring them back into the calendar.

The old /state folder content must be copied to /var/lib/z-push.

Z-push

Z-push is an open source implementation of Microsoft Exchange ActiveSync protocol. The actual version is 2.0.7-1690 (2013-02-18).

Since version 2.0.3XXX in file config.php is a new parameter FILEAS_ORDER:

  • define('FILEAS_ORDER', SYNC_FILEAS_LASTFIRST);

This parameter will define the sort order for the first contacts field Save as in Zarafa-WebAccess.

Check for sort order Lastname, Firstname LASTFIRST.

It will sync the Calendar, Contacts and Tasks to a mobile device, in my case Android operating system.

The update from z-push is very similar to a fresh installation. You just have to take care about the stage folder.

Please have a look at the Administrator Manual, chapter 5.5.5 Upgrade.

It is crucial to always keep the data of the state directory in order to ensure data consistency on already synchronized mobiles. Without the state information mobile devices, which already have an ActiveSync profile, will receive duplicate items or the synchronization will break completely.

# login via SSH from a terminal emulation
$ ssh 192.168.17.xxx

# move archive
$ mv Download/z-push-2.0.7-1690.tar.gz Install/Zarafa

# unpack archive
$ cd Install/Zarafa
$ tar xzvf z-push-2.0.7-1690.tar.gz 

# rename old folder, if not already there
$ sudo mv /var/www/z-push /var/www/z-push-2.0.6

# move new folder in place and symlink
$ sudo mv z-push-2.0.7-1690 /var/www/
$ sudo ln -s /var/www/z-push-2.0.7-1690 /var/www/z-push

# version remark
$ sudo touch /var/www/z-push/z-push-2.0.7-1690.txt

# adjust owner
$ sudo chown -R root:root /var/www/z-push/

# adjust rights of "state" folder
$ sudo chmod -R g+w /var/lib/z-push
$ sudo chown -R www-data:www-data /var/lib/z-push

# check for differences in config
$ sudo diff /var/www/z-push/config.php /var/www/z-push-2.0.6/config.php

-----------------------------------------
# Just in case of a NEW Installation ONLY, not for an update:
# Install with synaptic the packages: php5-imap, php-mail, php-mail-mime

# edit Apache config file with Midnight Commander
$ sudo mc /etc/apache2/httpd.conf
# append the following line:
  Alias /Microsoft-Server-ActiveSync /var/www/z-push/index.php
# save to file and exit mc

# restart apache web-server
$ sudo /etc/init.d/apache2 reload
 * Reloading web server config apache2

# setup check in file config.php:
define('FILEAS_ORDER', SYNC_FILEAS_LASTFIRST);

# if needed prepare logging folder:
$ sudo mkdir /var/log/z-push
$ sudo chmod a+w /var/log/z-push
$ sudo chown -R www-data:www-data /var/log/z-push

# Test with web browser, Zafara must already be running!
www.rudiswiki.de/Microsoft-Server-ActiveSync

# A login mask appears: Enter user name and password
# It must be the Zarafa user name and password, not the Ubuntu account.

Caveats:

Zarafa Client setup

Now, that the server is operating, the clients have to be setup.

SSL setup for Windows mobile

SSL setup for z-push is described in the manual, see links.

If you encounter problems (especially windows mobile phone), there is a German Howto "Generate private SSL certificate" for apache2, see the links. It is for general use, without being linked to Zarafa.

The generated certificates must be converted into DER format, as described in the last part of the z-push manual. Then copied to a windows mobile phone.

MAC OS X iCal setup

When you select Exchange Server in iCal, it can be setup, but will not be updated.

# The Exchange Server type does not work, use CalDAV
Account setup
Account type: Exchange server 2007
Account name: www.rudiswiki.de
User name   : zarafa-user:reuterru
Password    : zarafa-user:[password]
Calendar update: every 15 min

Server setup
Server address: 192.168.17.xx (web domain did not work)
Server path: /EWS/Exchange.asmx
Port: automatic
SSL: Yes

Offered sync type:
  Nothing

When you select CalDAV in iCal, it can be setup:

Account setup
Account type: CalDAV
Account name: Zarafa-CalDAV
User name   : zarafa-user:reuterru
Password    : zarafa-user:[password]

Server setup
Server address: 192.168.17.xx
Server path: /caldav/reuterru
Port: 8443
SSL: Yes

Offered sync type:
  Calendar
  Tasks

OK - It will sync both ways, every hour

Mac OS X contacts

The contacts (version 7.1) synchronization with cardDAV does not work.

Android Account use with ActiveSync

First you have to add a new account. In the main screen press key setup and account. Usually the googlemail account is shown. At the bottom of the screen you can tap on Add account. If you do you have several choice:

For contacts and calendar you have to select geschäftlich or Microsoft Exchange ActiveSync.

Android does not accept a port number in the URL.

You have to enter the following parameters (/Microsoft-Server-ActiveSync is appended to the URL):

# for in house use only
E-Mail address: reuterru@192.168.17.xx
or
# for Internet use with SSL
E-Mail address: reuterru@www.rudiswiki.de
Password: xxxxx  (zarafa-user-password)

No mark at "Send E-Mails from this account by default" -> next

mark at "Use SSL" 
# If you do not have a trusted certificate
mark at "Alle SSL-Zertifikate akzeptieren" (allow all certificates)
-> Finish

Mark at "Sync Calendar"
Mark at "Sync Contacts"

Calendar
When you create a new calendar appointment, you have to take care to select the active sync account. Otherwise it will not be synced. Changing the account later is not possible.

Contacts
In case you setup a new Zarafa data base, and your mobile phone does have a lot of contacts already in the address book, you need to do the following procedure to sync the contacts back to the server:

Unfortunately I have not read anything about that handling in the Zarafa/z-push documentation.

Thunderbird Calendar Add-On Lightning

Under Mac OS X I had a problem with installation. Lightning won't install completely. In the Thunderbird Profile-Folder in the folder extensions in the sub-folder stage you find the complete installation tree with the name {e2fda1a4-762b-4020-b5ad-a41df1933103}. This folder must be copied by the installation program to the folder extensions.

Unfortunately in my case that did not happen. So, I did it manually. Again, unfortunately not all files got copied. Especially some *.js files from the sub-folder components were missing. So, weird things happened after installation. The solution was to precisely copy all files from the stage folder to the target folder.

Problem solving with CalDAV access is described here.

Problem: Thunderbird was never asking for a password but yet was failing to authenticate as though I had typed one in. There could only be one reason ...

Password Manager !

I opened up Options --> Security --> Passwords --> Saved Passwords and clicked on the Show Passwords button.

There I could immediately see the source of my problems. The saved password for Zarafa access under my username was out of date.

Now it all made sense, as I had just last week changed my network password.

I highlighted the line, and deleted it.

As soon as I restarted Thunderbird, it prompted me for my username and password for the Calendar connection, and once again offered to store it in Password Manager.

Another troubleshooting topic for Lightning is here.

Zarafa Administration

In order to see, which users are setup, type:

$ sudo zarafa-admin -l

Free SSL trusted certificate

While the Android (Microsoft Exchange) ActiveSync client Geschäftlich in the Lenovo A1 (Android 2.3.3) tablet accepts the Ubuntu SSL certificate ssl-cert-snakeoil.key, the Android (Microsoft Exchange) ActiveSync client Microsoft Exchange ActiveSync in the LG P500 smart phone does not, even if the mark is set on accept all certificates.

An article in the German c't magazine from heise.de, see link, describes how to get a validated SSL certificate for free, for private use, see link. However, for that procedure you need an Email server on your server, for Email address postmaster@domain.com. You have to know, that the free certificate is valid for 1 year only.

If you are using because of cost reasons Dynamic DNS for your domain, you need a MX record. At my domain provider http://www.regfish.de this is possible:

# Add parameters for a MX-Record (MaileXchanger)
rudiswiki.de.  mail.rudiswiki.de.

Check this with http://www.mxtoolbox.com .

Next step is to open TCP port 25 SMTP in the firewall of you router, in order to access the server from Internet.
Check that with:

$ nmap www.rudiswiki.de
PORT     STATE  SERVICE
...
25/tcp   open   smtp
...

The last check is to send an Email to postmaster@rudiswiki.de. You can read the received Email on the terminal with program mutt.

Next you must generate your own key file:

openssl genrsa -out rudiswiki.de.key 2048

# Generate your Certificate Signing Request (CSR) file
openssl req -new -key rudiswiki.de.key -out rudiswiki.de.csr

Now you can get a free SSL certificate from http://www.startssl.com . The files you get are:

Certificate for web browser SSL_StartCom_xxxxxx.p12
Certificate ssl.crt  # rename to rudiswiki.de.crt
Intermediate: sub.class1.server.ca.pem
Root: ca.pem

# edit file: /etc/apache2/sites-available/default-ssl
 SSLCertificateFile    /etc/ssl/certs/rudiswiki.de.crt
 SSLCertificateKeyFile /etc/ssl/private/rudiswiki.de.key

# this will avoid client browser question for the certificate authority 
 SSLCertificateChainFile /etc/ssl/certs/sub.class1.server.ca.pem

# restart web server apache2
$ sudo /etc/init.d/apache2 restart

Important: If you do not want to further receive Emails, please close TCP port 25 SMTP in your router firewall.

Update Zarafa from 7.05 to 7.06

The update is done on an Ubuntu 10.04 server (2012-04-21).

A little help could be found here, or here.

# unpack
$ tar -xzf zcp-7.0.6-32752-ubuntu-10.04-i386-free.tar.gz

# Backup the config files
$ sudo cp -r /etc/zarafa /etc/zarafa705.bak

# Backup the database
$ sudo mysqldump --single-transaction -p zarafa > zarafa705.sql

$ cd zcp-7.0.6-32752-ubuntu-10.04-i386/

# Stop the Zarafa server
$ sudo /etc/init.d/zarafa-server stop
 * Stopping Zarafa server: zarafa-server 

# Do the update   
$ sudo dpkg -i lib* php* pyt* zarafa*

(Lese Datenbank ... 252694 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereiten zum Ersetzen von libical0 0.44-3 (durch libical0_0.44-3_i386.deb) ...
Entpacke Ersatz für libical0 ...
Vorbereiten zum Ersetzen von libical-dev 0.44-3 (durch libical-dev_0.44-3_i386.deb) ...
Entpacke Ersatz für libical-dev ...
Vorbereiten zum Ersetzen von libvmime0 0.9.2+svn603-1 (durch libvmime0_0.9.2+svn603-3_i386.deb) ...
Entpacke Ersatz für libvmime0 ...
Vorbereiten zum Ersetzen von libvmime-dev 0.9.2+svn603-1 (durch libvmime-dev_0.9.2+svn603-3_i386.deb) ...
Entpacke Ersatz für libvmime-dev ...
Vorbereiten zum Ersetzen von php5-mapi 7.0.5-31880 (durch php5-mapi_7.0.6-32752_i386.deb) ...
Entpacke Ersatz für php5-mapi ...
Vorbereiten zum Ersetzen von python-mapi 7.0.5-31880 (durch python-mapi_7.0.6-32752_i386.deb) ...
Entpacke Ersatz für python-mapi ...
Vorbereiten zum Ersetzen von zarafa 7.0.5-31880 (durch zarafa_7.0.6-32752_all.deb) ...
Entpacke Ersatz für zarafa ...
Vorbereiten zum Ersetzen von zarafa-client 7.0.5-31880 (durch zarafa-client_7.0.6-32752_i386.deb) ...
Entpacke Ersatz für zarafa-client ...
Vorbereiten zum Ersetzen von zarafa-common 7.0.5-31880 (durch zarafa-common_7.0.6-32752_i386.deb) ...
Entpacke Ersatz für zarafa-common ...
Vorbereiten zum Ersetzen von zarafa-contacts 7.0.5-31880 (durch zarafa-contacts_7.0.6-32752_i386.deb) ...
Entpacke Ersatz für zarafa-contacts ...
Vorbereiten zum Ersetzen von zarafa-dagent 7.0.5-31880 (durch zarafa-dagent_7.0.6-32752_i386.deb) ...
 * Stopping Zarafa LMTP dagent: zarafa-dagent       [ OK ] 
Entpacke Ersatz für zarafa-dagent ...
Vorbereiten zum Ersetzen von zarafa-dev 7.0.5-31880 (durch zarafa-dev_7.0.6-32752_i386.deb) ...
Entpacke Ersatz für zarafa-dev ...
Vorbereiten zum Ersetzen von zarafa-gateway 7.0.5-31880 (durch zarafa-gateway_7.0.6-32752_i386.deb) ...
 * Stopping Zarafa gateway: zarafa-gateway          [ OK ] 
Entpacke Ersatz für zarafa-gateway ...
Vorbereiten zum Ersetzen von zarafa-ical 7.0.5-31880 (durch zarafa-ical_7.0.6-32752_i386.deb) ...
 * Stopping Zarafa ical gateway: zarafa-ical        [ OK ] 
Entpacke Ersatz für zarafa-ical ...
Vorbereiten zum Ersetzen von zarafa-indexer 7.0.5-31880 (durch zarafa-indexer_7.0.6-32752_i386.deb) ...
 * Stopping Zarafa indexer: zarafa-indexer          [ OK ] 
Entpacke Ersatz für zarafa-indexer ...
Vorbereiten zum Ersetzen von zarafa-libarchiver 7.0.5-31880 (durch zarafa-libarchiver_7.0.6-32752_i386.deb) ...
Entpacke Ersatz für zarafa-libarchiver ...
Vorbereiten zum Ersetzen von zarafa-libs 7.0.5-31880 (durch zarafa-libs_7.0.6-32752_i386.deb) ...
Entpacke Ersatz für zarafa-libs ...
Vorbereiten zum Ersetzen von zarafa-licensed 7.0.5-31880 (durch zarafa-licensed_7.0.6-32752_i386.deb) ...
 * Stopping Zarafa licensed: zarafa-licensed        [ OK ] 
Entpacke Ersatz für zarafa-licensed ...
Vorbereiten zum Ersetzen von zarafa-monitor 7.0.5-31880 (durch zarafa-monitor_7.0.6-32752_i386.deb) ...
 * Stopping Zarafa monitor: zarafa-monitor          [ OK ] 
Entpacke Ersatz für zarafa-monitor ...
Vorbereiten zum Ersetzen von zarafa-server 7.0.5-31880 (durch zarafa-server_7.0.6-32752_i386.deb) ...
 * Stopping Zarafa server: zarafa-server    No /usr/bin/zarafa-server found running; none killed. [fail]
Entpacke Ersatz für zarafa-server ...
Vorbereiten zum Ersetzen von zarafa-spooler 7.0.5-31880 (durch zarafa-spooler_7.0.6-32752_i386.deb) ...
 * Stopping Zarafa spooler: zarafa-spooler          [ OK ] 
Entpacke Ersatz für zarafa-spooler ...
Vorbereiten zum Ersetzen von zarafa-utils 7.0.5-31880 (durch zarafa-utils_7.0.6-32752_i386.deb) ...
Entpacke Ersatz für zarafa-utils ...
Vorbereiten zum Ersetzen von zarafa-webaccess 7.0.5-31880 (durch zarafa-webaccess_7.0.6-32752_all.deb) ...
Site zarafa-webaccess disabled.
Run '/etc/init.d/apache2 reload' to activate new configuration!
Entpacke Ersatz für zarafa-webaccess ...
Richte libical0 ein (0.44-3) ...
Richte libical-dev ein (0.44-3) ...
Richte libvmime0 ein (0.9.2+svn603-3) ...

Richte libvmime-dev ein (0.9.2+svn603-3) ...
Richte zarafa-client ein (7.0.6-32752) ...

Richte zarafa-common ein (7.0.6-32752) ...
Installiere neue Version der Konfigurationsdatei /etc/cron.daily/zarafa-client-update ...
Richte zarafa-contacts ein (7.0.6-32752) ...
Richte zarafa-libarchiver ein (7.0.6-32752) ...

Richte zarafa-libs ein (7.0.6-32752) ...

Richte zarafa-monitor ein (7.0.6-32752) ...
Installiere neue Version der Konfigurationsdatei /etc/zarafa/quotamail/usersoft.mail ...
Installiere neue Version der Konfigurationsdatei /etc/zarafa/quotamail/userwarning.mail ...
Installiere neue Version der Konfigurationsdatei /etc/zarafa/quotamail/userhard.mail ...
Installiere neue Version der Konfigurationsdatei /etc/init.d/zarafa-monitor ...
 * Starting Zarafa monitor: zarafa-monitor         [ OK ] 

Richte zarafa-server ein (7.0.6-32752) ...
Installiere neue Version der Konfigurationsdatei /etc/zarafa/ldap.openldap.cfg ...
Installiere neue Version der Konfigurationsdatei /etc/zarafa/ldap.active-directory.cfg ...

Konfigurationsdatei »/etc/zarafa/server.cfg«
 ==> Modifiziert (von Ihnen oder einem Skript) seit der Installation.
 ==> Paketverteiler hat eine aktualisierte Version herausgegeben.
   Was möchten Sie damit machen? Ihre Wahlmöglichkeiten sind:
    Y oder I : Die Version des Paket-Betreuers installieren
    N oder O : Die momentan installierte Version beibehalten
       D     : Die Unterschiede zwischen den Versionen anzeigen
       Z     : Prozess in den Hintergrund, um die Situation zu begutachten
 Der Standardweg ist das Beibehalten der momentanen Version.
*** server.cfg (Y/I/N/O/D/Z) [Vorgabe=N] ? 
Installiere neue Version der Konfigurationsdatei /etc/init.d/zarafa-server ...
 * Starting Zarafa server: zarafa-server             [ OK ] 

Richte zarafa-spooler ein (7.0.6-32752) ...

Konfigurationsdatei »/etc/zarafa/spooler.cfg«
 ==> Modifiziert (von Ihnen oder einem Skript) seit der Installation.
 ==> Paketverteiler hat eine aktualisierte Version herausgegeben.
   Was möchten Sie damit machen? Ihre Wahlmöglichkeiten sind:
    Y oder I : Die Version des Paket-Betreuers installieren
    N oder O : Die momentan installierte Version beibehalten
       D     : Die Unterschiede zwischen den Versionen anzeigen
       Z     : Prozess in den Hintergrund, um die Situation zu begutachten
 Der Standardweg ist das Beibehalten der momentanen Version.
*** spooler.cfg (Y/I/N/O/D/Z) [Vorgabe=N] ? 
Installiere neue Version der Konfigurationsdatei /etc/init.d/zarafa-spooler ...
 * Starting Zarafa spooler: zarafa-spooler          [ OK ] 

Richte zarafa-utils ein (7.0.6-32752) ...
Richte php5-mapi ein (7.0.6-32752) ...
Richte python-mapi ein (7.0.6-32752) ...

Richte zarafa-dagent ein (7.0.6-32752) ...
Installiere neue Version der Konfigurationsdatei /etc/init.d/zarafa-dagent ...
 * Starting Zarafa LMTP dagent: zarafa-dagent      [ OK ] 

Richte zarafa-dev ein (7.0.6-32752) ...
Richte zarafa-gateway ein (7.0.6-32752) ...
Installiere neue Version der Konfigurationsdatei /etc/init.d/zarafa-gateway ...
 * Starting Zarafa gateway: zarafa-gateway         [ OK ] 

Richte zarafa-ical ein (7.0.6-32752) ...
Installiere neue Version der Konfigurationsdatei /etc/init.d/zarafa-ical ...
 * Starting Zarafa ical gateway: zarafa-ical       [ OK ] 

Richte zarafa-indexer ein (7.0.6-32752) ...
Installiere neue Version der Konfigurationsdatei /etc/init.d/zarafa-indexer ...
 * Starting Zarafa indexer: zarafa-indexer         [ OK ] 

Richte zarafa-webaccess ein (7.0.6-32752) ...
Installiere neue Version der Konfigurationsdatei /etc/zarafa/webaccess-ajax/config.php ...
Enabling site zarafa-webaccess.
Run '/etc/init.d/apache2 reload' to activate new configuration!

Verarbeite Trigger für man-db ...
Verarbeite Trigger für ureadahead ...
Richte zarafa ein (7.0.6-32752) ...
Richte zarafa-licensed ein (7.0.6-32752) ...
Installiere neue Version der Konfigurationsdatei /etc/init.d/zarafa-licensed ...
 * Starting Zarafa licensed: zarafa-licensed       [ OK ] 

Verarbeite Trigger für python-support ...
Verarbeite Trigger für libc-bin ...
ldconfig deferred processing now taking place
 
# Check the version
$ zarafa-server -V
Product version:        7,0,6,32752
File version:           32752

# update Apache2
$ sudo /etc/init.d/apache2 reload

$ ps -A
...
23256 ?        00:00:00 zarafa-monitor
23291 ?        00:00:05 zarafa-server
23340 ?        00:00:00 zarafa-spooler
23342 ?        00:00:00 zarafa-spooler
23381 ?        00:00:00 zarafa-dagent
23383 ?        00:00:00 zarafa-dagent
23417 ?        00:00:00 zarafa-gateway
23418 ?        00:00:00 zarafa-gateway
23452 ?        00:00:00 zarafa-ical
23454 ?        00:00:00 zarafa-ical
23487 ?        00:00:01 zarafa-indexer
23638 ?        00:00:00 zarafa-licensed
...

# webaccess OK

WebAccess

WebAccess is a tool to maintain your communication data in the data base. It is modeled after MS Outlook.

It is called via https://www.server.de/webaccess.

Unfortunately Firefox version 15 does not allow a redirect. So, after typing in your login data you have to click on Reload and then click on allow to redirect to the webaccess page.

In Mac OS X web browser Safari (OS X 10.8.2) there is no problem to login.

Webapp 1.0 BETA

A new webaccess version 1.0 is anounced. You download file webapp-1.0.tar.gz . The minimum Zarafa version must be 7.0.6.

$ cd Download

# unpack
$ tar -xzf webapp-1.0.tar.gz

# rename
$ mv packages zarafa_webapp_packages

$ cd zarafa_webapp_packages/debian

# install
$ sudo dpkg -i zarafa-webapp_7.1.0-33778_all.deb

# change owner
$ cd /var/lib/zarafa-webapp/
$ sudo chown -R www-data:www-data tmp

# tell apache2
$ sudo /etc/init.d/apache2 reload

# show login mask
# Firefox URL: https://www.rudiswiki.de/webapp

Troubleshooting

$ sudo zarafa-stats --system
0x3001001E              0x6740001E                                                   0x6741001E
-------------------------------------------------------------------------------------------------
server_start_date       Time when the server was started                 Mon May 20 09:17:17 2013
cache_purge_date        Time when the cache was cleared
config_reload_date      Time when the configuration file was reloaded / logrotation (SIGHUP)
connections             Number of handled incoming connections                          18261
max_socket              Highest socket number used                                      29
redirections            Number of redirected requests                                   0
soap_request            Number of soap requests handled by server                       114039
response_time      of soap requests handled in milliseconds (includes time in queue)    297686
processing_time    Time taken to process soap requests in milliseconds (wallclock time) 284631
...

List of pages in this category:

... -- RudolfReuter 2012-01-10 19:46:52

Go back to CategoryAndroid or StartSeite ; KontaktEmail (ContactEmail)

ActiveSyncZarafa (last edited 2015-06-15 15:21:24 by RudolfReuter)