[Kolab-devel] Specify Kolab IP address

[Gunnar Wrobel]

"Andrew J. Kopciuch" <akopciuch at bddf.ca> writes:

>> > however ... those services are written based on whether you have the
>> > service turned on or off.   and the SERVICE entry seems to be hard coded
>> > within the PERL Kolab::Conf library. 
>> > /kolab/lib/perl/vendor_perl/5.X.x/Kolab/Conf.pm
>> >
>> > I did some experimenting, and adding additional options after the
>> > @@@cyrus-pop3s@@@ seems to get left out.   I do not know the internals of
>> > kolabconf overly well, so maybe someone with more experience there could
>> > comment?
>> >
>> > Currently the listen=143" option is written, and it listens on all IPs,
>> > and what you seem to want is listen="my.single.ip.address:143" or
>> > something similar.   You could permanently change the cyrus.conf
>> > template, and grab the entire written config lines, and replace the
>> > @@@cyrus-*@@@ meta tags.
>> >
>> > That would work, but you would loose control of turning those services on
>> > and off through the LDAP options (used in the admin site, or kolabadmin
>> > etc.).
>>
>> There is no need to remove the @@@cyrus-pop3s@@@ entries. But you'd
>> need to edit the content within those lines within the template in
>> order to reduce binding to specific intefaces.
>>
>> While kolabconf does not use a particularly strong template language
>> the problem in this case is rather that the template does not cope for
>> different bind IPs. So in this case there is no alternative to editing
>> the template.
>>
>> Cheers,
>>
>> Gunnar
>>
>
> What I was saying, is that is how the other templates work, and I was 
> surprised that this is not the case with the cyrus.conf.template.   
>
> I tried adding listen="some.ip.address:143", and other options to those lines 
> to see if that would in fact help the original poster.  After running 
> kolabconf, they are not written to the actual cyrus.conf.  It works in other 
> templates like main.cf.conf to append text after a META TAG like this :
>
> @@@postfix-whatever@@@ some additional options.
>
> I tested the cyrus.conf.template adding options to both prefix, and suffix the 
> META TAG, but it seems that if that META TAG value is set in LDAP, the entire 
> line is overwritten with a hard coded service command string 
> from : /kolab/lib/perl/vendor_perl/5.X.x/Kolab/Conf.pm.
>
> In fact ... if you modify the tag name to something that does not exist, your 
> additional text is printed instead of a command line, but if the meta tag 
> name is valid, your additional text is not written to the config file.
>
> The real problem here is that you can not adjust the cyrus.conf template to 
> make the services bind to a single IP address, because kolabconf seems to 
> overwrite the service commands with a hard coded default, and ignores 
> additional text on those service lines from the template.

Yes, you are right and I did overlook that this is a special
template. kolabconf probably needs some modifications to allow binding
to specific interfaces. You should probably open a bug about this.

Cheers,

Gunnar

>
> The only option I can see to stop that from happening is to replace the meta 
> tags with the actual command lines you want, binding to a single IP address.  
> And the only downside is you would loose the ability to turn services on / 
> off through LDAP (admin interface / kolabadmin).
>
>
>
> Andy
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel

-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at p at rdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~