Problem/Query: If you type an address into the address field of a new Notes mail and it will be completed to a Notes Name, or you choose a name from NAB you will get a result in a Notes Name like “First Last/ORG” … Okay.
If you hit F9 then, you will get the REAL addressing.
If this is a normal user with a local mailbox in the domain, you will get either the full qualified address including Notes mail domain like “First Last/ORG@DOM” or the internet SMTP address like “first.last@org.com” - That’s what we like to see.
BUT - If the user entry in the NAB got a forwarding address in the person doc, you will get the forwarding address like “first.last@other.com” instead of the full qualified oder Internet SMTP Address , that we expect.
QUESTION: How can we suppress this ?!
This forwarding address must only be visible and functional for the server routing process, not for the client.
We found some poor documented notes.ini settings that are misleading and do not work for this. But those are pointing in a similar direction:
SPR# SJAR6GA3HT - New functionality was added SMTPTranslateAddressLookup=2 to allow lookups to the secondary directories to translate internet addresses that are defined in a secondary directory, to their hierarchical name. The ini is to be used in conjunction with SMTPTranslateAddresses=2 and also requires Router Address Lookup in the Configuration document is set to Fullname Only. This SPR is fixed in 7.0.2
SPR# MPUL6ZHHRS - When using the Notes.ini variable “SMTPTranslateAddresses” to translate internet addresses to Notes addresses in the addressing fields, if a forwarding address exists, then by default the translation will use the forward address. Added a new notes.ini variable “SMTPTranslateNoForward” to control the functionality during address translation, so that it will not use the forwarding address if specified. When SMTPTranslateNoForward=1, it will use of the first value in the User Name field even if a Forwarding Address is present. Without the notes.ini, the default behavior is to use the forwarding address if one is present in the person document. This SPR is fixed in 8.0.1
As said, this is misleading. We are looking for a parameter the other way round.
We like to translate the Notes Name to the internet address and NOT to the forwarding address.
Unfortunately, there is currently no feature to prevent Notes-format addresses from converting to Forwarding Addresses when pressing F9 in a memo.
An enhancement request for this functionality has been submitted here:
As a workaround to achieve your requirement—preventing the Notes address from converting to the recipient’s actual address upon pressing F9 while still ensuring the email is forwarded to the intended address—you can use a mail rule. Please follow the steps below:
Remove the forwarding address from the Person document.
Create a mail rule in the user’s mail file with the following settings:
Condition: When All Documents
Action: send Full copy to
Run the following server commands if the address still converts when pressing F9:
load updall -R names.nsf
tell router update config
show nlcache reset
Please keep the following points in mind:
Messages sent to the user will also be delivered to their local mail file.
I had the experience a few years ago that if a user had set up forwarding (for example, because they were on vacation) and you sent them a message during that time, the forwarding address was also saved in the recent contacts of the personal address book. As a result, even after the forwarding had ended, emails were still being sent to the wrong recipient.
However, I do not know whether this is still the case.
this is even worse, if a different, may be private forwarding address becomes public.
An internal sender sends an email to a list of recipients, one of them is forwarded, one of them is external. This forwarding address will also be populated to the external recipient who knows the “other” address from this point. The address might be completely off-context from the sender’s company. On reply to all will this forwarding address be used, the reply will never reach the origin address, but direct the forwarding address.
In my opinion this is a complete no-go in enterprise mailing. A forwarding address must never be populated.
Today we are forced to use an add-on-tool to adjust the behaviour and block and manipulate the addresses in outbound mails.