Kolab 3.4 Multi-Domain and ptloader
Brady, Mike
mike.brady at devnull.net.nz
Wed Dec 2 23:01:09 CET 2015
On 2015-12-03 01:19, Jan Kowalsky wrote:
> Hi Cornelius, hi Mike,
>
> Am 24.11.2015 um 17:09 schrieb Cornelius Hald:
>> Hi Mike,
>>
>> unfortunately I've no solution for your actual problem. I just wanted
>> to let you know that I'm running a multi-domain setup with Kolab 3.3
>> and enabled ptloader.
>>
>> With 3.3 there was an issue that ptloader could crash quite often, but
>> AFAIK this has been resolved in 3.4. So yes, I think this combination
>> s
>> hould be possible.
>
> If you speak about https://issues.kolab.org/show_bug.cgi?id=4979 - my
> experience was, it isn't resolved in 3.4.
>
> I'm on Debian. I added the Patch of Franz Skale and everything works
> fine.
>
> The Patch - I took from
> https://obs.kolabsys.com/package/show/home:connyhald:branches:Kolab:3.3:Updates/cyrus-imapd
> and actualized it for 3.4 is here:
>
> https://obs.kolabsys.com/package/show/home:jankowalsky:branches:Kolab:3.4:Updates/cyrus-imapd
>
> Cornelius, do you made the experience it works out of the box with 3.4?
> Maybe then it's still an debian issue?
>
> Best Regards
> Jan
Jan
I don't know if what I encountered was this bug, but I believe that
there are multiple bugs.
1) ptloader was sending an LDAP query that has an incorrect base DN and
therefore received no result.
2) ptloader crashed because it received no result.
I found that setting the "Custom Root DN" to the appropriate base dn in
kolab_webadmin sets the inetdomainbasedn attribute in LDAP and that the
LDAP queries are then correct.
Regards
Mike
More information about the users
mailing list