a few more questions

[Gustavo Michels]

Em Wednesday 08 September 2004 19:16, Jean-Michel Dault escreveu:

> I solved these issues in Kolab 1.0. The hardest part was to hack kolab
> so it reads the old entry before doing any modification, so it can use
> the original ObjectClasses and doesn't erase the attributes it doesn't
> know.

Well, to be honest, I think I don't need the kolab web interface to manage 
my users, I could do that thru any ldap admin tool, as I am using. Of 
course hacking kolab so that it would be compliant to my changes would be 
great, but on the other hand, I don't plan to make my changes using 
permanent OUs such as ou=Users or ou=Groups to hold my user's data.

Anyway, I would still be using the web interface for the rest of the 
administrative tasks.

> Another challenge was to be able to "toggle" system user status. That
> is, by default, the user is only inetOrgPerson, but you can switch it to
> a system account. I created a KolabExtendedSchema auxiliary class that
> has all the attributes of posixAccount, shadowAccount and
> sambaSamAccount as MAY, instead of MUST.

Well I simply added the person, posixAccount and shadowAccount attributes to 
the objectClasses, but your solution is cleaner.

> There are a couple of problems if you don't have the @domain part in the
> user id:
> 1) You have to manually change the freebusy configuration so it uses an
> e-mail address, but authenticates with the uid.
> 2) You have to modify sasl so it only search on the uid, not the e-mail,
> otherwise, if someone tries to authenticate with his email, it will
> create the mailbox with the e-mail, and that results in two mailboxes
> per user and support problems.
> 3) You'll have to modify the vacation code not to specify any e-mail
> address, otherwise cyrus crashes (I don't know why, but it does).

As I said, I didn't spent much time testing yet, so I can't tell if the 
above issues happen to me. IIRC, Kolab used to require the e-mail to be the 
uid, but on the recent snapshots I am testing (1 week old), this is not 
required anymore, so maybe the above issues doesn't happen anymore.

Anyway, I will test those 3 problems as soon as I can.

cheers
Gustavo