The Best Open Source Email & Collaboration Software

Deutsch Deutsch down

Frequently Asked Questions - Install / Update

Using the zarafa-admin tool you can modify user information.

Log on to the Zarafa server using PuTTY (or another SSH client) or directly with a console and give the following command:

zarafa-admin -u <username>
[-U <new username>]
 
[-p <new password>]

The settings between [ ] are optional and can be used to modify the following properties:

-U <new username>

Modify a users username.

-p <new password>

Modify a users password.

-e <e-mail>

Modify a users primary email address.

-f <full name>

Modify a users full name.

-a <0|1>

With this option you can set whether a user is an administrator. 0 disables admin rights, 1 enables admin rights.

 

Hints and tips

If you don’t know the exact username in Zarafa, you can view all users by giving the following command:

zarafa-admin –l

The Zarafa server use by default port 236. To use an encrypted connection you need to enable port 237 and create ssl certificates.

The webaccess runs on the a default Apache webserver, so port 80 or 443.

When SELinux is enabled, this is blocking your connection from the webserver to the Zarafa server.

You may solve this by allowing Apache to make network connections:

setsebool httpd_can_network_connect=1

or by disabling SELinux altogether:

setenforce permissive

When you choose to disable SELinux, you will also want to edit /etc/sysconfig/selinux to disable it for reboots too.

 

Hints en Tips

More information about Selinux can be found here: http://fedora.redhat.com/docs/selinux-faq/

A update from Debian GNU/Linux 4.0r3 "Etch" and Ubuntu 8.04 will remove Zarafa, by upgrading libvmime0

Calculating upgrade... Done
The following packages will be REMOVED:
zarafa zarafa-webaccess
The following NEW packages will be installed:
libgsasl7
The following packages will be upgraded:
libvmime0
1 upgraded, 1 newly installed, 2 to remove and 0 not upgraded.
Need to get 944kB of archives.
After unpacking 16.2MB disk space will be freed.
Do you want to continue [Y/n]?

 

Since the libvmime API of 0.7 and 0.8 is completely different, we indeed hold the upgrade from Debian Etch back.

However, this is not an issue, since no other package in Debian depends on 0.8. You can set the libvmime0 package on hold with the command

echo libvmime0 hold | dpkg --set-selections

There are three different user plug-ins for Zarafa; the UNIX, the LDAP and the internal DB plug-in:

* The UNIX plug-in uses information from /etc/passwd, /etc/group and /etc/shadow. This means that only the Linux users can get access to Zarafa. By setting a uid range of wich users are added to Zarafa. In the same way you can add groups to Zarafa. Users with a special shell (default /bin/false) will be added as non-active user. With the Unix plug-in is it necessary to add additional information like email address, admin option and user quota settings in the database. This information needs to be added to the database with the Zarafa-admin tool. The uid would be stored in the data to make a link between the Linux users and the information in the database.

* The LDAP plug-in uses information from a LDAP or ADS server. All information about users, groups and membership can be retrieved from the LDAP or ADS server. The managing of the users and groups has to be done in LDAP or ADS. Only the uid would be stored in the Zarafa database, other data would receive from LDAP or ADS.

* The DB plug-in would be installed by default and need no more configuration. All user information would store in the database. The managing has to be done with the zarafa-admin tool.

Sending a file of 2Mb or larger using the Webaccess is not possible by default. This is caused by a limitation in PHP, which is the language used to build the Webaccess. The limit of PHP can be enlarged, but this should be done in the PHP configuration file.

When you want to send an email with an attachment larger than 8 MB, you can still use Outlook which doesn't have this limitation.

The value which needs to be changed in the php.ini file is: 'max_upload_filesize'.

max_upload_filesize = 16M

Technically this is possible, but you always need to have a commercial Zarafa package for Outlook support. These packages are only available for the default supported distributions.

Zarafa has been developed purely for Linux. However, if you are a developer, you may help us by providing the probably small but necessary changes to Zarafa, so it will run on your platform.

No, the Zarafa 6.0x and 6.1x clients are forward compatible with the new 6.20 version. However, you will still need a license.

When a new user is added to the server, the standard folders are created in the language of the server. When you want to change the standard folders for a user to a different language, you have to change the /etc/zarafa/userscript/createuser script. This has to be done before the user is created in the Zarafa database.
If you want to change the standard folders to, for example, Dutch (nl_NL) you can add the following line to the createuser script:

export LC_MESSAGE=nl_NL.utf8

or replace ‘zarafa-admin --create-store "${ZARAFA_USER}"’ with:

zarafa-admin --lang nl_NL.utf8 --create-store "${ZARAFA_USER}"

When you are using Debian, you have to install the locales before you change the createuser file:

dpkg-reconfigure locales

When the standard folders of an existing user are in the wrong language, they can be changed with Outlook (XP/2003 or higher) to the correct language. It is important that the language of Outlook is the same as the language that you want for your standard folders.

* Close Outlook
* Click on Start > Run
* Type here: Outlook.exe /resetfoldernames

Outlook will start with the standard folders in the same language as Outlook. From now on the standard folders will be in this language.

To upgrade a single company to a multicompany environment where all existing users are placed into the same company, the following actions must be taken:

Make a backup of the Zarafa database. Enable multicompany in the Zarafa configuration files. Restart the Zarafa server. Create a new company, using LDAP or the zarafa-admin tool.
Use zarafa-admin --list-companies to make sure the new company is visible in the new environment. Stop the Zarafa server.

Note: The following 3 queries are only needed when the server has version 6.1x or 6.2x.

Execute the following SQL queries in the Zarafa database:

UPDATE users SET company = (SELECT id FROM users WHERE object_type=4)
WHERE (object_type = 1 OR object_type = 2 OR object_type = 5) AND id > 2;

UPDATE stores SET company = (SELECT id FROM users WHERE object_type=4)
WHERE user_id > 2;

UPDATE stores SET user_id = (SELECT id FROM users WHERE object_type=4) ,
user_name = (SELECT externid FROM users WHERE object_type=4) WHERE user_id = 1;

Note: The following query needs to be executed for every multicompany version (6.1x and up).
When using the DB plugin, the following query is also required:

SELECT p.value FROM object AS o JOIN objectproperty AS p ON o.id=p.objectid
WHERE o.objecttype = 4 AND p.propname='companyname'

INSERT INTO objectproperty (objectid, propname, `value`) SELECT id,
'companyid', (SELECT p.value FROM object AS o JOIN objectproperty AS p ON
o.id=p.objectid WHERE o.objecttype = 4 AND p.propname='companyname') FROM
object WHERE objecttype != 4;

After this the Zarafa server can be started again, and the users should be, once again, visible with:

'zarafa-admin -l'

 

Jobs at Zarafa

View zarafa tour 2013 video

Zarafa customers