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
Most other applications add the TLS Version and used cipher to the received header.
Example:
from xyz.acme.local (10.100.1.234) by abc.acme.local (10.100.109.233) with Acme SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1261.35; Tue, 17 Jul 2018 07:22:15 +0200
It would make sense that Domino adds this to the received header as well!
And maybe into a separate text list indicating the message was transport encrypted
Daniel Nashed [ https://blog.nashcom.de ]
Why only inbound? I would need it Outbound as well
Attachments Open full size
If I understand my customer regarding the requirements by law or regulatory (GDPR), it could be a 1st step to have an indicator that documented that a mail send with "TLS". A customer must prove that TLS (Transport Layer Security) is used for their domains.
Attachments Open full size
Case Number : TS001337027
Company Name : PRM only-Finanz Informatik
Note : Customer Also needs the feature of recording / logging TLS or STARTTLS in Log.nsf if mail was routed via TLS.
Attachments Open full size