Re: modify rule in ldap routing (second try)

In article <eb8b9f$d5b$1@xxxxxxxxxxxxxxxxxxxx> Martin
<ug211ai@xxxxxxxxxxxxxxx> writes:

To solve this problem I've made the following modification in proto.m4:
modify rule in ldap routing
diff proto.m4 proto.m4.orig
1035c1035
< R$+ < @ $={LDAPRouteEquiv} . > $: $>LDAPExpand <$1 < @ $2 . >>
<$1+$2 @ $M> <>',
---
R$+ < @ $={LDAPRouteEquiv} . > $: $>LDAPExpand <$1 < @ $2 . >>
<$1 @ $M> <>',

[snip]

Now I can benefit from the `strip' parameter from FEATURE(`ldap_routing'):
"`strip' tries the lookup with the +detail and if no matches are found,
strips the +detail and tries the lookup again."

[snip]

Is this a good idea to handle such exceptions ?

Modifying the m4 "source" files will always be a pain, as you will need
to re-apply the mods on upgrade rather than just carrying your .mc file
along.

Are there any undesirable side effects of this rule modification ?

Doubling the number of LDAP lookups for almost all recipients would
probably be considered undesirable by most, but I guess it depends on
your traffic load if this is a significant problem.

For the first drawback, I believe you should be able to put a custom
rule in a LOCAL_RULE_0 section of your .mc file to achieve a similar
result. Unlike the proto.m4 mod, it would have to "permanently" modify
the recipient address, but if you don't have addresses that should "pass
through" the LDAP lookup, it shouldn't matter.

For the second drawback, you could make such a custom rule (or for that
matter your proto.m4 mod) more specific, and only modify the addresses
that really need it (and not use the 'strip' parameter) - but of course
this takes a piece of configuration information out of your LDAP and
puts it in your sendmail config, which may or may not be an acceptable
trade-off for you.

--Per Hedeland
per@xxxxxxxxxxxx
.

Relevant Pages

  • Re: modify rule in ldap routing (second try)
    ... "`strip' tries the lookup with the +detail and if no matches are found, ... The number of LDAP Lookups for the maillocaladdress attribute is doubled ... it would have to "permanently" modify ...
    (comp.mail.sendmail)
  • Re: Reversing display name in GAL
    ... an LDAP export and modify the ldif file with scripts the import it back in. ... That can be risky if you are not familiar with LDAP import/export. ... The display name is generated at creation time, ... > the Display Names of the Active Directory Users via MS ...
    (microsoft.public.exchange.admin)
  • Re: Servers dependent on Active Directory
    ... I'm happy with the infrastructure too. ... appliance has the IP address of a DC hard coded to do LDAP lookups. ... and you just don't understand what those reason were just yet. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Servers dependent on Active Directory
    ... appliance has the IP address of a DC hard coded to do LDAP lookups. ... SPAM filtering appliances. ... and you just don't understand what those reason were just yet. ...
    (microsoft.public.windows.server.active_directory)
  • Re: LDAP and Public Folders
    ... I'm not sure how HP Digital Sender works in terms of LDAP lookups, ... Public Folder entries will be located in the Microsoft Exchange System ...
    (microsoft.public.exchange.admin)