Nathan Christenson | 25 Jan 18:56 2015

Calendar synchronization - kontact and roundcube

Hello everyone,

I am having some configuration issues with kolab 3.3, installed on Ubuntu from the kolab package repository, and I am hoping the list can help me work through these.

Domain setup
I currently have the server setup as follows: roundcubemail at one url (, and the other kolab-related services on another url ( The 389 server is running on localhost, cofigured with an third domain name (if that matters), my FQDN ( The webservers, imap and smtp are all secured (not the LDAP server).

Question: FQDN versus servers
My FQDN is where LDAP, IMAP and SMTP are configured to listen - so, when asked for an IMAP or SMTP server, that is what I put in the dialog. However, this does not match the web-based access to kolab services, which are available at a different url. Is this causing some of th eissues below? What's the recommended / required way to set up kolab if I've got it wrong? Should all the services (IMAP, SMTP, LDAP) listen on

Issue 1: Roundcubemail cannot access chwala
I changed the configuration in the "" configuration file to point to "" (instead of the default) - roundcubemail displays an error on the screen Connection Error: (Failed to Reach Server!); however, if I type into my browser, chwala works just fine. It also works well via WEBDAV.

Issue 2: kontact setup
I setup a new account in kontact (I use Arch LInux - Kontact 4.14.4) - I created the account in korganizer>settings>add>. For me, there are two choices - "kolab groupware server (legacy)", which is labeled as obsolete and seems to match the dialogs shown in most of the documentation I've found online (chossing between v2 and v3 formats, for example), and "kolab groupware server". I chose "kolab groupware server", which asked for my imap server and login, but nothing else. What's was unexpected is that I have a Calendar folder and a Files folder that show up as IMAP folders, and I get an email when I add a file to Chwala and some kind of notification I cannot access when I add calendar events in roundcubemail. The Calendar folder shows (2) unread messages, but shows as blank when selected.

Issue 3: calendar synchronization
My roundcubemail and Kontact calendars do not sync - I can add events to my personal calendar in each, but Kontact events do not display in roundcubemail and roundcubemail events do not show in Kontact. Adding and editiing contacts works just fine.

Issue 4: activesync / syncroton
In my current configuration, this doesn't work. Am I correct that I need to configure the web server so that syncroton is accessible through the webmail domain ( and not kolab? 

Thank you for any insight you can provide - I'd really appreciate it.

users mailing list
users <at>
Timo Posemann (RDG | 25 Jan 17:32 2015

Segmentation fault quota -f kolab 3.3

i have installed kolab 3.3 on debian 7. I used the kolab documentation 
I do a backend LDAP upload from 390 Users/Sharedfolders.

After that i login with a user and was able to see emails and all seen 
states of the imported old installation kolab 2.3 was okay. But 
roundcubemail shows no quota state of the mailbox, so i tried to connect 
with thunderbird to that mailbox. It was the same, all shows up 
correctly but no quota. So i decited to do a /usr/lib/cyrus-imapd/quota 
-f but it shows segmentation fault.
 From the old kolab2 i used the old cyrus.header, cyrus.cache and 
cyrus.index files for the reconstruct. So decited to give it another try 
and do not override cyrus.header, cyrus.cache and cyrus.index. At this 
time after the reconstruct i lost all seen state of the mails but had 
the correct quotas in roundcubemail and thunderbird.

Can someone help?

Best regards,


Timo Posemann
zero one | 25 Jan 10:43 2015

Kolab with dovecot 2.2.13, calendar problem


I have successfully installed dovecot 2.12.13 with kolab and everything is running fine exept of calendar. I can add events but I am not able to change calendars' color nor am I able to add additional calendars. In addition the calDAV link does not word.

The iRony log shows:
Sabre\DAV\Exception\NotAuthenticated (EXCEPTION);
No basic authentication headers were found

I assume I have some problems with the calendar UID an dovecot metadata. Did I miss anything in my configuration?

I followed this how-to:


users mailing list
users <at>
Rick | 24 Jan 18:46 2015

Steps to take to keep exiting mails from ending in destination junk box

I've got a fresh install debian wheezy x64 with Kolab 3.3 , I'm testing this system and sending emails to my
own addresses in gmail and microsoft.
They all end up in the junk mail folders.
What steps need to be taken to make sure emails being sent from a Kolab instance do not get flagged by these systems.

users mailing list
users <at>
Timotheus Pokorra | 23 Jan 14:47 2015

Question about upgrading cyrus-imapd in Kolab 3.3 Updates


this email is directed to all users of the Kolab 3.3 community packages.

We have a segfault bug in Cyrus Imap which is delivered with Kolab 3.3.

It has been discussed on this mailinglist:

There is also this bug for it:

Thanks to Gregory, we have a pull request for Kolab 3.3 Updates:

Since there is no other quality assurance for the community edition of 
Kolab other than us the community, I want to ask if some people can test 
this for a couple of days, before I merge the request into Kolab 3.3 

I am not using Kolab in production yet myself, so I don't feel in a 
position to make such a decision on my own.

To test the package suggested by Gregory, please add his repository:

-O kolab-3-test-new_cyrus.repo
yum update

Hmm, this does not work yet, because the package is not published yet.

 <at> Gregory: can you please publish the packages for testing? go to
and in section "Publish Flag" make sure that All/All has a green mark, 
with right click you get a popup menu to select that.

When enough people say this works for them, I will be happy to merge 
this pull request into Kolab 3.3 Updates, and everyone will be using 

Henrik Bohr | 20 Jan 13:37 2015

How to migrate data from kolab 3.2 to kolab 3.3 ?

Dear all,

recently I tried to migrate the data from my running (but buggy) kolab 3.2 installation to a new kolab 3.3 installation. However all information I found about migration was for migration from kolab 2 to kolab 3. After many difficulties and the new installation not recognizing the copied emails I finally gave up.

Does anyone know a tutorial on how to migrate from one kolab 3.x to another kolab 3.x? Or is there maybe somebody who really knows kolab and could explain me (and probably many others) how to do such a migration?

It would be great if somebody has an answer!

Thanks a lot,
users mailing list
users <at>
Cornelius Hald | 19 Jan 07:31 2015

Re: Segmentation fault (SEGV) in cyrus ptloader / CentOS 7

Thanks for the info Jan. It is not that easy to find good information
about ptloader and Kolab :)


On Thu, 2015-01-15 at 10:58 +0100, Jan Kowalsky wrote:
> Hi Cornelius,
> Am 12.01.2015 um 12:29 schrieb Cornelius Hald:
> > On Fri, 2015-01-09 at 22:20 +0100, Jan Kowalsky wrote:
> >> Hi all,
> >>
> >> Am 02.01.2015 um 10:33 schrieb Cornelius Hald:
> >>> Hi Franz,
> >>>
> >>> I'm not having any update on that. Also there seems to be no activity on
> >>> the bugs if filed. What I find strange is that there are not more
> >>> complains about that. In my opinion crashes like that should be treated
> >>> with very priority - but maybe it is hare to reproduce?!
> >>
> >> just for information: yes I do complain. I just disabled ptloader for
> >> the moment because it doesn't work for me neither.
> > 
> > Are there any side effects if you disable ptloader completely?
> This was the suggested approach for the multidomain-setup before cyrus 2.5
> but we got the problem that then cyrus is unable to proof the canonical
> names of users if one is adding a new acl.
> So users could add acls (via roundcube or mailclient) for user subjects
> into cyrus db which don't exist. In the worst case your cyrus db is
> corrupted.
> I wrote a bug-report about this behaviour:
> Maybe there are other impacts if canonification of user subjects don't work.
> Best Regards
> Jan
Dirk Davidis | 15 Jan 11:27 2015

Kolab and IPAServer


i recognised that there are some attempts, to combine Kolab with an
already existing IPA Server on the same System. I read all the
statements about that, but at the end i didnt found out any stragedy.

Maybe someone can tell me how to do this.

users mailing list
users <at>
gregory.bahde | 18 Jan 13:56 2015

Segfault on centos6 using kolab 3.3

since I upgraded to kolab 3.3
 I get often segfaults:
ctl_mboxlist[2837]: segfault at 10 ip 00007f38fd37161f sp 00007fffe0abde38 error 4 in[7f38fd23e000+18a000]

and rebooting I have python traceback:
   File "/usr/lib64/python2.6/multiprocessing/", line 232, in _bootstrap
<goon__> Process PoolWorker-13:
<goon__> Traceback (most recent call last):
<goon__>   File "/usr/lib64/python2.6/multiprocessing/", line 232, in _bootstrap
<goon__> Process PoolWorker-14:
<goon__> Traceback (most recent call last):
<goon__>   File "/usr/lib64/python2.6/multiprocessing/", line 232, in _bootstrap
<goon__> Process PoolWorker-15:
<goon__> Traceback (most recent call last):

any idea?


greg bahde

De: users-request <at>
À: users <at>
Envoyé: Dimanche 18 Janvier 2015 12:00:02
Objet: users Digest, Vol 131, Issue 22

Send users mailing list submissions to
        users <at>

To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to
        users-request <at>

You can reach the person managing the list at
        users-owner <at>

When replying, please edit your Subject line so it is more specific
than "Re: Contents of users digest..."

Today's Topics:

   1. Howto delete a parent Domain? (Reitelbach, Thomas)
   2. Re: Howto delete a parent Domain? (Timotheus Pokorra)

users mailing list
users <at>

users mailing list
users <at>
Reitelbach, Thomas | 17 Jan 15:33 2015

Howto delete a parent Domain?

Hello list,

I've setup kolab 3.3 on centos 6.6 just fine. Using the 
multi-domain-scripts I have configured kolab to serve 4 independent 
parent domains and I must say: everything is working just fine and as 

But now I have the need to remove one of the parent domains. In kolab 
3.1 I was able to do this using the web administration panel, but in 
kolab 3.3 the responsible button is missing (or at least I can't find 

So can anyone help me what is the preferred way to delete a parent 
domain from kolab?
I have simply NO idea how ldap itself works and thus I am stuck with the 
web panel. Removing the corresponding IMAP mailboxes is no problem for 

Thanks for advise...
Thomas | 16 Jan 15:58 2015

R: Re: Kolab behind a NAT

It worked really well: I had to install more "reverse proxies" (one for iRony, 
one for kolab-webadmin, one for roundcubemail, etc..), but using this 
"proxies", and the X-Forwarded-For Header all but one problems went away!

Many thanks!

The only problem is just iCal: the URL generated start with a ./?
_task=calendar&_action=feed&_cal= and the code of the calendar. Putting this 
code as is  isn't working (just as expected, there isn't any reference to my 
base URL). It doesn't show even on my LAN connection, I'm doing some more thing 
wrong? Thank you for your patience :)

>----Messaggio originale----
>Da: ar <at>
>Data: 16/01/2015 14.51
>A: "Kolab Users Mailinglist"<users <at>>
>Ogg: Re: Kolab behind a NAT
>I have a similar setup. You have to pass the X-Forwarded-For Header to your 
>kolab server
>You need to add
>      proxy_set_header     Host              $http_host;
>      proxy_set_header     X-Real-IP         $remote_addr;
>      proxy_set_header     X-Forwarded-For   $proxy_add_x_forwarded_for;
>regards, Axel 
>Am Freitag, 16. Januar 2015, 11:24:44 schrieb alby87 <at>
>> Hi! Thanks to all your suggestion, my Kolab installation is working fine!
>> Well, almost :) I've a little problem: Kolab is installed inside a
>> dedicated (virtual) machine with his own private IP, and is behind a
>> router. Just natting the correct port to the server, all the service are
>> working goods, the problem is all about the http services, as they should
>> share the company website with another machine. I configured a reverse
>> proxy in Nginx, (and I will put the configuration below) to have the
>> "normal website" managed by it, and all the things related to Kolab
>> redirected to the right machine.
>> The problem is: some http service don't work as they should: the "show
>> calendar URL" use internal IP (, and if substitute with
>> it works, but I can't (for example) update
>> the calendar. Also the preview on webmail didn't work, and also the files
>> section on Roundcube. What's the correct strategy? I have tought of one,
>> but I need a confirmation: 1)Create on the main webserver as many reverse
>> proxies as "directory" used by Kolab (one for roundcube, one for
>> kolab-admin, etc...) 2)Change the /etc/network/hosts file to connect to our
>> public IP
>> But this would create a URL, where I would
>> prefer the
>> Hope I don't have confused you with my request :)
>> My Nginx configuration about the reverse proxy
>> location /webmail {		proxy_pass;		
>> 40M;	}
>> Many thanks :)
>users mailing list
>users <at>