Fedora directory users - Feb 2009 - mail aliases in directory

I''m in the process of migrating to keeping all users and
mail aliases in a directory server. For people-objects we use the
object classes ''top'', ''person'' and
''mailRecipient'', but I''m a bit
confused as to how to store pure email aliases that are not
connected to specific accounts.

I think we''ll want to store these in a separate ou (ou=aliases), 
but what''s the correct set of object classes to use ?
''mailRecipient''
gives me all the attributes, but isn''t structural. I found the
ldapSubEntry structural class that seems fitting (gives me structure, 
and nothing else), but from reading the deployment guide that seems
to not be what we want.. (doesn''t show up in normal searches).


# dn: mail=test@example.com,ou=aliases,o=example.com,o=ISP,o=mydomain,c=NO
# changetype: add
# objectClass: ldapSubEntry
# objectClass: top
# objectClass: mailRecipient
# mail: test@example.com
# mailForwardingAddress: test@sometherdomain.net


Any hints to what class should be used here instead of ldapSubEntry?



  -jf

Jan-Frode Myklebust wrote:
> I''m in the process of migrating to keeping all users and
> mail aliases in a directory server. For people-objects we use the
> object classes ''top'', ''person'' and
''mailRecipient'', but I''m a bit
> confused as to how to store pure email aliases that are not
> connected to specific accounts.
> 
> I think we''ll want to store these in a separate ou (ou=aliases), 
> but what''s the correct set of object classes to use ?
''mailRecipient''
> gives me all the attributes, but isn''t structural. I found the
> ldapSubEntry structural class that seems fitting (gives me structure, 
> and nothing else), but from reading the deployment guide that seems
> to not be what we want.. (doesn''t show up in normal searches).
ldapSubEntry has very specific semantics and should not be used for any
normal user application entry.

I''d recommend to create your own STRUCTURAL object class with just
attribute ''mail'' for the list of MUST attributes.

Ciao, Michael.

On 2009-02-04, Michael Ströder <michael@stroeder.com>
wrote:
>
> ldapSubEntry has very specific semantics and should not be used for any
> normal user application entry.
>
> I''d recommend to create your own STRUCTURAL object class with just
> attribute ''mail'' for the list of MUST attributes.
OK, thanks! Also included mailForwardingAddress as a MUST:

objectClasses: ( mailAlias-oid NAME ''mailAlias'' SUP top
STRUCTURAL
	MUST ( mail $ mailForwardingAddress ) X-ORIGIN ''user defined''
)


  -jf