Package Details: zarafa-server

Git Clone URL: (read-only)
Package Base: zarafa-server
Description: Open Source Groupware Solution
Upstream URL:
Keywords: grouware mailserver
Licenses: AGPL3
Groups: zarafa
Provides: zarafa-server-arm=
Replaces: zarafa-server-arm
Submitter: xtfxme
Maintainer: martimcfly (jelly)
Last Packager: martimcfly
Votes: 6
Popularity: 0.000000
First Submitted: 2009-10-13 18:39
Last Updated: 2018-06-02 08:52

Dependencies (75)

Sources (9)

Pinned Comments

martimcfly commented on 2018-08-20 13:08

Go ahead here:

martimcfly commented on 2018-06-04 09:38

This package is not maintained anymore. Zarafa has changed its company's name to Kopano. Please update to kopano-* packages. I hope to see you over there ;) Thanks!

For those willing to update to the latest Zarafa version: The last version possible to compile this packages with is Archlinux from the 24.04.2017. Following pacman entries can be used (please remove default mirrors).

[core] Server =$arch/$repo

[extra] Server =$arch/$repo

[community] Server =$arch/$repo

[alarm] Server =$arch/$repo

[aur] Server =$arch/$repo

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

rolek commented on 2014-12-18 08:33

We're running Zarafa on Slackware and we have the same problem. We've seen that the problem occurs a lot less often if we ensure no connections are made to the zarafa-server process before it is fully started. So, our Zarafa startup procedure now looks like:
- Stop postfix
- Disable access to the unix socket**
- With iptables, drop incoming traffic to ports 236 and 237
- Start zarafa-server
- Wait for 10 seconds
- Start the other zarafa daemons
- Allow incoming traffic to ports 236 and 237
- Allow access to the unix socket
- Start postfix

** On our system, the socket path is /var/run/zarafa/zarafa, so this is easily done by changing the access right on the /var/run/zarafa dir. On Arch, this might be different.

I hope this is useful to you.

jelly commented on 2014-11-03 19:03

Got the same problem here, not sure what the issue is. Looking into it with upstream :-)

martimcfly commented on 2014-10-29 17:54

On ARM 7.1.11 just exited right after start. That's why I didn't integrate it.

sushifrick commented on 2014-10-29 16:06

Does anyone else have the problem, that the zarafa-server deamon dies quite often since the last update?

"Caught SIGABRT (6), out of memory or unhandled exception, traceback"

It also happens, when there is plenty of memory left (>2GB), using loglevel 5 does not give me any extra information.

I tried increasing some cache sizes in the server.cfg but without any luck. zarafa-stats shows me there should be enough cache size left.

martimcfly commented on 2014-10-02 14:48

You can contribute to this package:

jelly commented on 2014-08-17 17:50

Sorry I was misinformed the mariadb is required, added it back

jelly commented on 2014-08-10 18:36

Sorry for the delay:
- md5sum fixed
- mariadb patch not needed anymore
- man-page removed

martimcfly commented on 2014-08-08 23:55

you can get it from zarafa-server-arm package or from the aur git repository.

toco commented on 2014-07-10 16:38

how can I isnstall the older version with

* a correct md5 sum
* a patch included
* and the mariadb patch

Anonymous comment on 2014-06-16 08:28

Thank you for the update. However, the package seams to be broken, now:
* a md5 sum does not match
* a patch does no longer apply
* the mariadb patch is not included anymore