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.
same here.
I am talking about the forwarding address.
In my first example to an internal domain to provide a co-existance of two systems.
This forwarding address toward the other local mail system cannot be routed in the internet, because it is a not fully qualified domain and strictly internal.
If a local Notes sender sends a mail to recipients who are a) local, b) local with a forwarding to the internal domain and c) external, all recipients will receive the mail. Fine. But all recipients see recipient b with the forwarding address.
On Reply, this forwarding address, will now be used by any person who replies . This can also be the external user who can not route to the forwarding address! The error occurs!
As a second example: If we set a forwarding for an address like "my.name@my.company.com" toward to "my.name@theother.company.com" we DO NEVER like to make theother.company public in the context of my.company. External sender must always address me at my company domain.
For my opinion this must be configurable in an enterprise mailing system.
I guess you are talking about a forwarding address in the person document?