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
$MessageID disparities for same message to different recipients
Issue details: Installed Software: Work Server 10.1.1 R2 (101.1.38) cluster Work Server Config for duplicate detection: Duplicate Detection Type: 2 Server-Side Duplicate Detection: Y Server-Side Duplicate Detection Type: 0 WorkSite Communication Server 9.0 SP1 for Lotus Notes (90.1000.6) EM for Lotus Notes 93.1.86 DeskSite 93.4.43 OffSite 93.4.39
How to reproduce the Email Duplicates: 1. Send and File a mail to an internal recipient and an external recipient.
2. The mail will be filed to iManage; in this case the MSG ID is: OF1A243DA6.44F8EBF3ONC12582EF.006896D3C12582EF.email@example.com
3. The internal recipient's Inbox filer within Lotus Notes will also file the received mail into iManage -> no duplicate detection. MSG ID if this mail is: OF1A243DA6.44F8EBF3ONC12582EF.006896D3C12582EF.006933D7@LocalDomain
Further Information / status (from iManage investigation)
Message id of the same email in my Inbox: <OFD60E6F6D.56B66206-ON6525830D.003E64CD-6525830D.003E6ADE@LocalDomain>
Because of this, duplicate detection is failing. If the user imports the message from their Inbox more than once, duplicate detection works fine, as the message id is identical. We're investigating why Domino server would stamp different message ids to different copies of the same message. We're also investigating if a there is a workaround available to work around this issue. I've reach out to Engineering for the current status update that I will share with you.
IBM has reached out to us on behalf of the Customer to develop a possible solution with duplicate email detection; as there is a difference in the MessageID value when comparing the same email from the user's inbox with the one sent to the COM Server. We use the MessageID as a unique identifier in our duplicate detection process.