Proposed addition to draft-lachman-laser-ldap-mail-routing-02.txt

From: Richard Rognlie (richard@sendmail.com)
Date: Tue Apr 17 2001 - 07:05:38 PDT


There are two features that I have run into during data migration
to LDAP based routing from systems that use other mechanisms.

One is the use of +detail in user addresses.

e.g. richard+detail@sendmail.com

on some email systems, this implies that, the mail is for
richard@sendmail.com, and intended to be delivered directly to
user.richard.detail IMAP folder. Or on procmail systems, you
can use the +detail as part of your recipes.

I would propose that the lookup scheme be modified to first look
for

        mailLocalAddress = richard+detail@example.com

as it currently does. If that fails, strip and save the +detail
(if present), and lookup

        mailLocalAddress = richard@example.com

If found, route mail to the resulting mailRoutingAddress/mailHost.
(I'd like to see the original +detail reappended to the resulting
mailRoutingAddress, but that could be optional)

And finally, if not found, do the wild-card query

        mailLocalAddress = @example.com

The second feature has to do with this latter query. If the
query returns a mailRoutingAddress of the form

        @example.org

This implies that all mail for xyz@example.com should be routed
to xyz@example.org. Call it domain aliasing, virtual hosting,
whatever you like. It would certainly help keep ldap administration
of shared hosts down to a minimum. e.g. I run three domains
example.{com,net,org}. I want all mail for those three domains
for all of my users to go to example.com.

        dn: cn=wildcard,dc=example,dc=net
        objectClass: top
        objectClass: inetLocalMailRecipient
        mailLocalAddress: @example.net
        mailRoutingAddress: @example.com
        cn: wildcard

        dn: cn=wildcard,dc=example,dc=org
        objectClass: top
        objectClass: inetLocalMailRecipient
        mailLocalAddress: @example.org
        mailRoutingAddress: @example.com
        cn: wildcard

I could, of course, declare exceptions for the various domains as
well, but the wildcard does all of the remaining work.

With the above, richard@example.{com,net,org} are all the same
entity.

-- 
 /  \__  | 
 \__/  \ | Richard Rognlie / Sr. Technical Consultant / Sendmail, Inc.
 /  \__/ | http://www.gamerz.net/rrognlie/    <rrognlie@gamerz.net>
 \__/    |



This archive was generated by hypermail 2.1.2 : Thu Oct 24 2002 - 10:31:46 PDT