Chapter 8. Zarafa

8.1. Groupware Configuration

In this module you can optimize memory (RAM) for Zarafa, define the size of attachments or the content of quota emails for users.

Click "Optimize" to optimize the memory settings on your system. This is only necessary if the size of the RAM changes. The RAM settings will be optimized for Zarafa and MySQL.

You can also set the maximum size of attachments uploadable via the Zarafa Webaccess Interface.

[Note]

This limitation does not override the setting of the mailserver. If there is a smaller size of attachments allowed, the mailserver settings are effective.

At the tab "Messages At Reaching Quota" you can customize the messages for reaching limits. The description of variables is available at the online help.

The following variables are available:

Variable Meaning

${ZARAFA_QUOTA_NAME}

name of the Zarafa account

${ZARAFA_QUOTA_STORE_SIZE}

current size of the account

${ZARAFA_QUOTA_WARN_SIZE}

limit for a warning

${ZARAFA_QUOTA_SOFT_SIZE}

limit for a transmission lock of the account

${ZARAFA_QUOTA_HARD_SIZE}

limit for a transmission AND reception lock of the account

8.2. Resources

In this module you can create and delete resources. For deleting or modifying right-click on an existing resource and choose an action.

Please note at the creation of a new resource: A resource needs a name - this name is shown in the global adressbook - and a description. You may decide whether a resource can be booked once ("Decline Conflicts") and whether recurring appointments are permitted.

[Important]

If you want to change resource settings, you may change the properties and description but not the name!

8.3. Zarafa Setup

The configuration of yaffas & ZARAFA is done via the known interface. There are some specifics to explain:

As a matter of principle each user account in yaffas is also a Zarafa user. Please pay attention that you have a corresponding license of yaffas and of Zarafa. If you have less Zarafa user licences than yaffas users, only the users with the lowest UIDs have access to Zarafa.

8.4. Allocation of Email Addresses

The registered address at "Email Address" is also used as sender for all mails sent via web access. For a proper function please set the local domain(s) on the mailserver at first(menu Mailserver→ Configuration → Local Domains).

8.5. Zarafa WebAccess/WebApp

Insert the URL into your browser, e.g. https://zarafaserver.local/webaccess for webaccess. To reach the WebApp interface to to https://zarafaserver.local/webapp

A complete manual and current documentation of Zarafa WebAccess and WebApp can be downloaded here: http://www.zarafa.com/doc.

8.6. Zarafa Backup

With this module you can create brick-level backups of your zarafa data. You are afterwards able to restore single elements of the stores.

For the module to be usable it is necessary to manually install the package zarafa-backup (RedHat-based systems: yum install zarafa-backup, Debian-based systems: apt-get install zarafa-backup)

To create the backup select a time and day for the full and differential backup. You can select a directory on the server where you want to save the backups and configure a preserve time. After that timespan old backups will be deleted.

To restore elements select the day from you wish to restore you element and open the store and folder you need. Then add a folder or element to restore list by using the context menu. After you have selected all elements for restore you have to start the process in the restore tab.

[Important]

If you mount a share to the backup directory, make sure that symlinks are supported. If this is not the case, then differential backups are not possible and the system will do full backups.

8.7. Microsoft Outlook Connection

The client you need for connecting Microsoft Outlook is in "software" at the directory "zarafa" on your yaffas system. Please use exactly this version of the client, because it is matched with the Zarafa version used in yaffas. After updating yaffas you should always take the current version of the client out of this directory.

First, install the client on the Windows computer by double-clicking on "zarafaclient.exe" Please note: You must have administration permissions.

Start Outlook and choose the topic "Email Accounts" from menu "Extras" Create a new email account.

images/en/guides_zarafa_connect1.png

Server type must be "Additional Servers"

images/en/guides_zarafa_connect2.png

If you installed zarafaclient.exe from CD, you must now choose "Zarafa Server" If you are not able to choose "Zarafa Server", please install the Zarafa client first.

images/en/guides_zarafa_connect3.png

Please insert the data of your yaffas & ZARAFA server. You can use port 237 for an encrypted transmission (standard) or port 236 for an unencrypted connection. Use username and password like set in yaffas.

images/en/guides_zarafa_connect4.png

Please make sure that the following setting is made for the new account: "New Messages Send to" must match "Inbox User" Close Outlook and start it again. Now you can access your store and use mail, calendar or contacts… .

[Note]

Please understand that we are not able to give support to any issue of using, configuring or installing Microsoft Outlook!

8.8. Backup Path

At this point we show an unspecific way to backup the data of the server. For a successful recovery of the data the yaffas server must be on the same level of version and patches!

the paths for the backup of yaffas & ZARAFA are:

path entry

/var/log/

log-files

/data/mail/

mail boxes and Sieve filter scripts

/var/lib/fetchmail/.fetchmail-UIDL-cache

if fetchmail is used with POP3

Database MySQL (mysqldump)

all data of the Zarafa Server

/data/zarafa/

email attachments

Procedure for backup of data:

  • backup of configuration via system → save configuration
  • init 1 → change to single user mode
  • backup of single paths in a temporary directory
  • init 2 → normal mode of use
  • backup of data to an external data medium

Procedure for recovery of data:

  • recovery of configuration via system → save configuration
  • copy the data into a temporary directory
  • init 1 → change to single user mode
  • delete all files below the named paths
  • restore of single paths out of the temporary directory
  • init 2 → normal mode of use

For additional information on Zarafa backups, please refer to: http://doc.zarafa.com/7.1/Administrator_Manual/en-US/html/_full_database_dump.html