Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Validating users with multiple email addresses when the LDAP server is Domino in InterScan Messaging Security Suite (IMSS)

    • Updated:
    • 7 Jan 2016
    • Product/Version:
    • InterScan Messaging Security Suite 7.1 Windows
    • InterScan Messaging Security Suite 7.5 Windows
    • Platform:
    • Linux - Red Hat RHEL 3 32-bit
    • Linux - SuSE version 10
    • Unix - Solaris (Sun) version 10 (SunOS 5.10)
    • Unix - Solaris (Sun) version 9 (SunOS 5.9)
    • Windows 2000 Server
    • Windows 2003 Enterprise Server
Summary

When IMSS is configured to use Domino as the LDAP server, it will query the Internet Address field to verify the recipient's email address. However, if the user has more than one email address, IMSS will only acknowledge the first one in the list and ignore the aliases.

This article demonstrates how to validate a user with more than one email address.

Details
Public

The current IMSS design does not consider additional addresses or aliases when Domino is the LDAP server.

To resolve this, additional addresses must be exported to a file, which is used to feed the IMSS or Mail Transfer Agent (MTA).

For Linux/UNIX

If you are using Postfix, use the exported list to create a mapping file of valid recipients. Use the following parameter:

relay_recipient_maps

For more information about this parameter, refer to this Postfix document: Postfix Configuration Parameters.

Rejecting invalid recipients on the MTA will save you bandwidth and resources for handling junk email. Alternatively, you can check if Postfix or any other MTA can be configured to use Domino LDAP while considering the additional addresses per user.

For Windows

The only possible way to filter out such mails is to use policies after the mail is initially accepted. Do any of the following:

  • The first policy you will create should have "Any sender" and "Any recipient". The Exceptions should have "From internal address list to any" and "From any to internal address list". The conditions should match anything and the action is delete. All emails that are not from an internal user nor addressed to an internal user are removed or quarantined.
  • Create all your policies using address groups in the recipient section. The last policy should delete all of the remaining mails which are not handed off in one of the previous rules. This serves as a "catch all" rule. However, do not forget a final action before valid emails can hit the last rule. Otherwise, you will loose the legitimate emails.
Premium
Internal
Rating:
Category:
Configure; Troubleshoot
Solution Id:
1038175
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.