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
@Daniel Nashed
Thank you Daniel for you comment. We are very grateful for the in-depth information you provide on your blog and in various presentations. We have been following and using information from you for years now!
Our scenario is that we need to do a server-side DLP check of e-mails - even encrypted e-mails. The DLP check is done by custom c-api external manager. For checking encrypted e-mails this external manager assumes that a copy of e-mali should be addressed to special user called dlp@xxx.xx (the server.id has S/MIME private key for this special user imported). In order for this idea to work the e-mail should arrive at server in once piece, because when it is split then only one of the splits is encrypted for dlp@xxx.xx and can therefore be checked by DLP module and all other splits are unreadable by server.id
Now, this idea works perfectly with iNotes - no problems here. But from client the S/MIME encrypted e-mail is split for even as low a 3 reciepients (2+dlp@xxx.xx) with exactly the same encryption capabilities. Of course each recipient has 'prefer mime' setting, plus they have mail files on the same server. Personal address book does not hold any entries for this recipients.
If iNotes can send mail without splitting it ,why Notes client must do the split? This is a big mystery for us.
Please notice there is yet another idea (not ours) on that subject of mail splitting when sent from Notes client (although it does not involve encryption):
https://domino-ideas.hcltechsw.com/ideas/NTS-I-1267
Kind regards,
Michal Szuniewicz
What is your underlying issue?
There are many reasons mails might be split into different actual e-mails with separate recipients lists. It's not the number of recipients alone.
For example when you send mail to internal and external recipients, the mail will be spilt into a mail with Richtext and another one with MIME.
For encryption I would expect it to behave similar.
At least for Notes mail you should have one mail encrypted with a symmetric key for the mail which is encrypted with the public key of all recipients and the sender.
I would expect it to behave similar with S/MIME.
But here the devil could be in the detail. It could be that recipients have different encryption capabilities. I never looked into the details and it was never an issue.
People usually care about the upper limit for the number of recipients. Not about automatic splitting the mail when the list would be come to big.
Expanding an splitting also depends on settings. And using the large summary option on a client could introduce issues on a server, which might not have the setting.
So staying below the 32K summary item limit, makes sense and should not cause any issues if the splitting works.
Now again, what is your underlying problem? Why do you care for having one mail vs. splitted mails?
Each mail router by the way does also split the message for local delivery and different target servers.
The Notes mailer component is an back-end component of the Notes client which is around for a long time. But that doesn't mean it is not updated and maintained.
[Daniel Nashed / http://blog.nashcom.de ]