Page MenuHomeBlueprint

LDAP mailsystem schema notes

Authored by miroslaw on Jun 1 2016, 11:35.
* local and remote mail routing is explicitly out of scope of this
draft, at least right now; what I want to deal with is RECIPIENTS,
* …a RECIPIENT is associated with one PRIMARY MAIL ADDRESS, they may have
a MAILBOX, one or more LOCAL ALIASES and one or more FORWARDING
ADDRESSES; basically a RECIPIENT is a final destination on the mail
system that is being managed using this schema (let's call it “local”
for lack of a better word). Extensions in form of ${local_part}-* or
${local_part}+* may be allowed for both primary addresses and the local
aliases. Recipient settings may allow automatic spam marking and
filtering, and the object be administratively locked or black-holed.
Note: implementing local aliases safely will require administrative
controls that prevent the users from assigning random local addresses
to themselves – let's limit them to the local domain along with an ACL
restricting access to local alias attributes to a domain manager only,
perhaps? We can happily do without them anyway.
* …a DISTRIBUTION GROUP is a special case of RECIPIENT that serves
a group of users and that uses two or more local or remote FORWARDING
ADDRESSES. Usually there is no MAILBOX association. The distinction
between a RECIPIENT and a DISTRIBUTION GROUP is mostly functional.
* …a MAILBOX may use a path if it's somewhat local, may be local or
remote, can be served to the users via IMAP or POP, may be restricted
by quota, may allow sieve filtering and subfolders (for IMAP).
* So, one object class for recipients and distribution groups,
AUXILIARY, one object class for mailboxes, AUXILIARY, a typical user
object will combine inetOrgPerson, recipient and mailbox object
classes and their assorted attributes; a typical distribution group
may use either inetOrgPerson or groupOfNames, whichever is more

Event Timeline

miroslaw created this object with visibility "Public (No Login Required)".
miroslaw edited the content of this paste. (Show Details)