Present Perfect

Deep in the trenches of after-work experimenting because my work days do not allow me the time needed to investigate proper migration of our mail servers. Setting up Fedora Directory Server, which has some quirks but seems to be simpler to set up than OpenLDAP. Toying with getting Evolution to show Person objects defined in it, and allowing each person to edit themselves, I stumble across the problem of Evolution insisting on adding the "calEntry" objectClass to each object that I change a property of.

Some mails suggest that calEntry has an RFC but no "official" schema file, and that Toshok once made a patch to support this properly by checking the server for existence of this objectClass. That part was probably removed because it unconditionally tries to add this property value now.

Anyway, to get to the point. Evolution comes with an evolutionperson.schema file which you could load onto the server, but not with a calEntry.schema file, sadly. The evolutionperson.schema has this gem of a comment in it:

# spouseName
# single valued (/me smirks)
attributetype ( 1.3.6.1.4.1.8506.1.2.8
NAME 'spouseName'
SUP name
SINGLE-VALUE )


I guess way back when this file was written nobody expected Ximian to be taken over by Novell - a company originating from the heartland of mormonism.

Deep in the trenches of after-work experimenting because my work days do not allow me the time needed to investigate proper migration of our mail servers. Setting up Fedora Directory...