If you configure LDAP
acceptance queries, you may wish to bypass the acceptance query for certain
recipients. This feature can be useful if there are recipients for whom you
receive email which you do not want to be delayed or queued during LDAP
queries, such as
customercare@example.com .
If you configure the
recipient address to be rewritten in the work queue prior to the LDAP
acceptance query, (such as aliasing or using a domain map), the rewritten
address will not bypass LDAP acceptance queries. For example you use an alias
table to map
customercare@example.com to
bob@example.com and
sue@example.com . If you configure bypassing LDAP
acceptance for
customercare@example.com , an LDAP acceptance query is
still run for
bob@example.com and
sue@example.com after the aliasing takes place.
To configure
bypassing LDAP acceptance via the GUI, select
Bypass LDAP
Accept Queries for this Recipient
when you add or edit the RAT entry.
To configure
bypassing LDAP acceptance queries via the CLI, answer yes to the following
question when you enter recipients using the
listenerconfig -> edit -> rcptaccess command:
Would you like to bypass LDAP ACCEPT for this entry? [Y]> y
When you configure a
RAT entry to bypass LDAP acceptance, be aware that the order of RAT entries
affects how recipient addresses are matched. The RAT matches the recipient
address with the first RAT entry that qualifies. For example, you have the
following RAT entries: postmaster@ironport.com and ironport.com. You configure
the entry for postmaster@ironport.com to bypass LDAP acceptance queries, and
you configure the entry for ironport.com for ACCEPT. When you receive mail for
postmaster@ironport.com, the LDAP acceptance bypass will occur only if the
entry for postmaster@ironport.com is before the entry for ironport.com. If the
entry for ironport.com is before the postmaster@ironport.com entry, the RAT
matches the recipient address to this entry and applies the ACCEPT action.