Re: sendmail per-recipient routing
- From: yf110@xxxxxxxxxxxxxxxxxxx (Malcolm Dew-Jones)
- Date: 19 Jul 2005 12:59:39 -0800
Centurion (spam.this@xxxxxxxxxxx) wrote:
: We currently use a sendmail gateway with mailertable to route all mail to
: specific domains to the appropriate (internal) mail servers. We validate
: recipient addresses by scheduled rebuilds of the access list by pulling
: email addresses out of Active Directory. It all works very well :)
: However, I was asked this week if it is possible to refine the routing
: further to every recipient on our internal network - so members of "Group
: Boston" go to server "mail-boston", members of "Group Sydney" go to
: "mail-australia", etc but all addresses are part of the same external
: domain. eg,
: user1@xxxxxxxxxxx is a member of "Boston"
: user2@xxxxxxxxxxx is a member of "Sydney"
: users will never be members of more than one group.
: I know this is probably possible with LDAP Routing which would replace the
: current mailertable+access list configuration. My question to the group is
: simply what are some good online resources that *detail* setting LDAP
: routing against an Active Directory network? This should include any
: modifications necessary to AD.
: Dead-tree versions of $CLUE are also acceptable; I'm in Australia so ISBN
: and/or Title/Author/Publisher would be most helpful.
ooo, conceptually it isn't hard at all, but I did this long ago so I
forget the exact details.
If you look at your handy dandy sendmail manual then there are a series of
rule sets, S1 S2 etc. One of those rule sets is where the "delivery"
address is calculated. If you do a per-user lookup during that rule set
then you can re-direct individual users to any other address you wish.
(In effect they get relayed.) To use ldap, you simply include the ldap
setups with send mail, and then use the ldap lookup syntax to do the
lookup (instead of some other lookup syntax).
Before you try to do that, check the various pre-canned features. I
believe that "userdb" and "genericstable" can be used to set this up,
though I didn't use them at the time, so I can't suggest exactly how to
I did this by inserting a one line directly into the sendmail.cf file
(well one lookup and several error checks actually). The translation
table contained the canonicalized user addresses that need to be
translated, and the translation. The rule simply looked them up and used
the translation if one was found. As I said, that went into the rule set
that determines the delivery address, though I'm afraid I must leave the
exact location as an excersize for the reader. If you did an ldap lookup
then I assume you would need additional lines to ensure the address is in
the right format for the ldap lookup, and then the result would need to be
put back into the correct format for the sendmail rules, which is why
using the precanned features would be the place to start.
Hopefully someone else will give a more exact description of what to do.
This space not for rent.
- sendmail per-recipient routing
- From: Centurion
- sendmail per-recipient routing
- Prev by Date: Re: qmail+vpopmail to sendmail
- Next by Date: Re: Compiling sendmail 8.13.4 on AIX 5.1 ML7
- Previous by thread: sendmail per-recipient routing
- Next by thread: sendmail gets stuck in DATA mode