Multi-domain setup with Kolab 3.3 on CentOS 7

[Cornelius Hald]

Hi Sebastian,

that's really interesting. So you're not getting errors like this:
conn=29 op=4 SRCH dn="""" authzid="(null)", invalid dn

Are you on CentOS as well? Maybe your distribution comes with a
different version of Cyrus?

What puzzles me is that we all use the same Howto but get a broad range
of different results. Well, I'll do some more digging...

Thanks for the input!
Conny


On Tue, 2014-09-30 at 10:17 +0200, Sebastian Walter wrote:
> Hi Conny,
> 
> As I'm not using the multi-admin functionality regularly
> (multi-domain/single-admin instead), I'm not 100% sure but I followed
> the multi-domain how-to and everything works as expected.
> 
> The secondary domain users are able to login as well. I just tested the
> admin functionality for the secondary domains, too and they are able to
> create users, etc...
> 
> Regards,
> Sebastian
> 
> 
> 
> 
> On 09/30/14 10:02, Cornelius Hald wrote:
> > On Mon, 2014-09-29 at 20:50 +0000, Daniel Hoffend wrote:
> >>> If follow the steps under 'Cyrus IMAP Changes' for Kolab 3.2 and later,
> >>> I cannot log in to Roundcube with users of my secondary domain. Users
> >> >from the primary domain (the one created during setup) still can log 
> >>> in.
> >>>
> >>> However if I'm using the steps described for Kolab 3.1 and older, I'm
> >>> able to login those users.
> >> I've encountered the same problem. IMHO the current Cyrus IMAP 2.5 isn't
> >> fully able to do what roundcube does. It supports domain lookups but it
> >> doesn't support the a replacement for %dc in the member_base_dn 
> >> definition.
> >>
> >> I've reported this issue in the cyrus imap bugzilla:
> >> https://bugzilla.cyrusimap.org/show_bug.cgi?id=3860
> >>
> >> For now I would use the Kolab 3.1 way on how to configure cyrus to 
> >> support
> >> multi-domain usage.
> >>
> >> P.S.: I'm using Kolab 3.3 in a multi-domain setup with this method.
> > Thanks for the info! So basically my setup now works, but I'll run into
> > trouble regarding group membership?
> >
> > So it looks like the Kolab 3.2 way is still the way to go for Kolab 3.3.
> > Wonder why they wrote the documentation like it is now.
> >
> > Thanks!
> > Conny
> >
> >
> > _______________________________________________
> > users mailing list
> > users at lists.kolab.org
> > https://lists.kolab.org/mailman/listinfo/users
> _______________________________________________
> users mailing list
> users at lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users