new domains without changes to /etc/kolab/kolab.conf OR "pure" LDAP-only administration
Erik M Jacobs
erik at jumpshipservices.co
Mon Oct 7 02:09:14 CEST 2013
On 09/23/2013 06:12 AM, Timotheus Pokorra wrote:
> Hello Erik,
> See also the comment that I wrote just this morning:
> Related to this is this bug, that I am watching as well:
> I tried this morning to create a domain and user in that new domain
> without calling my adddomain.php script mentioned in the comment
> above, but had some other problems with trunk
> (https://issues.kolab.org/show_bug.cgi?id=2248). In the end, no
> mailbox was created.
> I think you still need the domain added in kolab.conf, since pykolab
> looks there for creating the imap mailbox and folders.
> But I am not completely sure about that.
Is there no way around this? That seems kind of like a flaw in the
model. In Zarafa, you simply set it to treat whatever LDAP object as a
company, and "users" within that object are mailboxes.
ou=somecompany.com, dc=somedomain, dc=net
ou=company2.com, dc=somedomain, dc=net
Having to edit a config file every time you add domains is not very
automation-friendly. Sure, whatever portal you're using could modify
the file, but then a config management system (puppet, chef, etc) would
have a hard time dealing with that file as well.
Anyone know if there are any plans to move away from that?
> All the best,
> On 23 September 2013 11:43, Torsten Grote <grote at kolabsys.com> wrote:
>> Hi Erik,
>> this is almost something for the development list. I remember, that Timotheus
>> (CCed) was working on automating the addition of new domains even more, but I
>> don't know what his efforts have led to.
>> Kind Regards,
>> On Saturday 21 September 2013 11:12:08 Erik M Jacobs wrote:
>>> Hi all,
>>> Looking at these docs:
>>> Specifically referring to #6:
>>> "The new domain has now been created in LDAP. For the web administration
>>> panel to pick up on various settings related to the new domain name
>>> space, edit /etc/kolab/kolab.conf and at a very minimum, add a new
>>> section for the new domain and set the base_dn setting."
>>> We're very interested in automation, and editing config files is a bit
>>> of a bear. Since most of what the admin interface does is update LDAP,
>>> if we're not "using" the admin interface to add/modify/etc., we wouldn't
>>> need to update the kolab config file, would we?
>>> In other words -- whatever Kolab's admin interface does to add new
>>> domains on the back-end, as long as we do the same thing in LDAP, we
>>> should be fine, right?
>> Torsten Grote, Kolab Evangelist
>> Kolab Systems AG, Zürich, Switzerland
>> e: grote at kolabsys.com
>> t: +41 43 501 66 91
>> w: http://kolabsys.com
>> pgp: 274D 4F97 Torsten Grote
>> users mailing list
>> users at lists.kolab.org
> users mailing list
> users at lists.kolab.org
More information about the users