Can alias_url1 Be Used To Cause Lookups In A Different User/Group Container? (Doc ID 2868927.1)

Last updated on FEBRUARY 23, 2024

Applies to:

Goal

Can alias_url1 be used to cause lookups in a different user/group container?

A "groupmailer" exists which runs as a pipe program.
The goal is to be able to do recipient validation of group recipient addresses, but...
The groups are defined in normal LDAP, but they have recipient addresses like "@group.example.com", but "group.example.com" is not defined in the DC tree. So these group objects are never found by the MTA's normal recipient address lookups.

A method was used to do this using LDAP lookups from ORIG_SEND_ACCESS, but that lead to trying to duplicate the MTA's normal LDAP error handling in mapping tables, which is difficult to test and, of course, much more complicated than one might think.

An idea of adding a proper dc=group under o=internet, with mailDomainDetourHostOptin and aliasoptindetourhost on channels on the ingress systems to route through the milter channel and then to the core-routing MTAs where the group pipe program runs, but that would be a big change.

What about alias_url1?
Should something like the following be a possibility to get this to work: alias_url1 = "ldap:///ou=groups,o=example.com,o=email?*?sub?$R"

and have the MTA normal recipient validation look for objects with mail=whatever@group.example.com under ou=groups,o=example.com, or does that still require group.example.com to have a valid domain DC tree definition?
 

Solution