Your message dated Mon, 27 Nov 2006 15:32:28 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#400594: please consider adding option to enable kolab support has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: gosa Severity: wishlist Hi Cajus How are you doing, hope you are doing well :) I am using gosa together with kolab here and it works fantastic. I was wondering if you want to add support for it into gosa. Below you can see what I added to the gosa package in sarge. Of course you can't include it as it is, but maybe you want to add a button or something else where one can enable these attributes for kolab. Cheers Steffen --- class_mailAccount.inc.orig 2006-11-27 13:16:11.000000000 +0000 +++ gosa-2.3/plugins/personal/mail/class_mailAccount.inc 2006-11-27 13:17:09.000000000 +0000 @@ -56,8 +56,8 @@ /* attribute list for save action */ var $attributes= array("mail", "gosaMailServer", "gosaMailQuota", "gosaMailMaxSize", "gosaMailDeliveryMode", "gosaSpamSortLevel", "gosaSpamMailbox", - "gosaVacationMessage", "uid"); - var $objectclasses= array("gosaMailAccount"); + "gosaVacationMessage", "uid", "kolabInvitationPolicy", "kolabHomeServer"); + var $objectclasses= array("gosaMailAccount", "kolabInetOrgPerson"); /* constructor, if 'dn' is set, the node loads the given
--- End Message ---
--- Begin Message ---Hi Steffen, this is not needed at all. Just switch your mail method in gosa.conf to "Kolab" and you're able to manage all aspects of your kolab installation. Accounts, lists, forwarders and even the server settings. BTW: Can you consider removing the slapd dependency from kolabd in unstable? It makes sense, if you use it the kolab way, but the kolab way sucks. No one puts the LDAP to the DMZ - or on the mail server. kolabd can be called by cron, too. Cheers, Cajus Steffen Joeris schrieb: > Package: gosa > Severity: wishlist > > > Hi Cajus > > How are you doing, hope you are doing well :) > I am using gosa together with kolab here and it works fantastic. > I was wondering if you want to add support for it into gosa. > > Below you can see what I added to the gosa package in sarge. Of course > you can't include it as it is, but maybe you want to add a button or > something else where one can enable these attributes for kolab. > > Cheers > Steffen > > --- class_mailAccount.inc.orig 2006-11-27 13:16:11.000000000 +0000 > +++ gosa-2.3/plugins/personal/mail/class_mailAccount.inc 2006-11-27 > 13:17:09.000000000 +0000 > @@ -56,8 +56,8 @@ > /* attribute list for save action */ > var $attributes= array("mail", "gosaMailServer", "gosaMailQuota", > "gosaMailMaxSize", > "gosaMailDeliveryMode", "gosaSpamSortLevel", > "gosaSpamMailbox", > - "gosaVacationMessage", "uid"); > - var $objectclasses= array("gosaMailAccount"); > + "gosaVacationMessage", "uid", > "kolabInvitationPolicy", "kolabHomeServer"); > + var $objectclasses= array("gosaMailAccount", "kolabInetOrgPerson"); > > > /* constructor, if 'dn' is set, the node loads the given > > >
--- End Message ---
