Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Under Consideration
Workspace Domino
Categories Integration
Created by Guest
Created on Dec 12, 2018

Domino Mail Forwarding Type ahead issue

From the SPR (SKJI7WMM4X) it is describe as:
"A user on the Internet sends a message to a Lotus Notes® user in your domain. The intended recipient of the message is defined in the Domino® Directory with a Person document specifying their mail system as "Other Internet Mail" with a
Forwarding Address populated. This forwarding address may be to a user outside of your Internet domain or to a user on another mail system internal to your domain. The message is properly received by this user at the address specified in
the Forwarding Address field in the Person document. However, when the recipient receives the message, it is addressed in the 'To' field to the recipient's original Internet address, not the forwarded address.
For example, if a message is sent to Joe Doe's Internet address of and Joe has a Forwarding Address of specified in his Person document, the message is forwarded, as configured. However, Joe Doe, when opening
the mail, sees in the 'To' field, and not
If Joe Doe's mail system is Notes®, the 'To' field will be, for mail coming from Notes or an alternate email application such as Microsoft® Outlook.
If the sender is a Notes user, the 'To' field will be, no matter what Joe Doe's mail system is."

  • Attach files
  • Guest
    Oct 18, 2022

    This is a real problem since this lead to SPF validation rejection (via DMARC) and the message is not routed to the final destination.

  • Guest
    Apr 21, 2020

    any update on this issue