Why does LDAP routing fail when the fully qualified domain name (FQDN) of the mail host matches the domain being routed?

Issue

Why does LDAP routing fail when the fully qualified domain name (FQDN) of the mail host matches the domain being routed?

Solution

This is a case in LDAP routing where having the domain to be routed (mira.example.com) same as the destination mailhost (mira.example.com), does not work well. For example:

mail: @mira.example.com

mailhost: mira.example.com

To correct the problem, try either of the following solutions:

• Have the mailhost attribute in LDAP point to the IP address of the appliance, instead of the fully qualified domain name (FQDN). For example:

mail: @mira.example.com

mailhost: 192.168.20.2

Or

• Use the setting Smtp Set Ldaprouting All, instead of Smtp Set Ldaprouting On. In this case, the destination domain should not be listed as a maildom. If there is a maildom entry for mira.example.com, it needs to be removed. Use the following command:

Maildom Delete mira.example.com