I understand it, but as mentioned on the given links, we should not rely or depend on third solutions, even from the same vendor, in order to achieve this.
One thing is Anti-Spam: It's completely understandable, as Domino mail is not aimed to be an Anti-Spam, however Domino supports querying to Black lists servers and other sources and we can always implement one in Gateway mode.
But, supporting an almost 7 years old protocol should be at core level already available.
Is there any technical reason why this may have not been delivered yet?
Hello Elvis, don't know any technical reason but somewhere I read that TLS 1.3 overhauls SSL/TLS in the way that TLS 1.0 should have and it is under consideration for inclusion in a future release of Notes/Domino.
Despite being the latest version, TLS 1.3 is not universally adopted yet. Many websites still use TLS 1.2, but major platforms like Google and Facebook have implemented TLS 1.3. All modern browsers support TLS 1.3, but it may not be enabled by default in all operating systems, such as Windows 10.
We probably have to wait for Windows 12 for the client side ;-)))
I spoke to the Product manager for Domino, and he explained it's quite a difficult subject. They ARE working on it. The request status (see https://domino-ideas.hcltechsw.com/ideas/DOMINO-I-124 ) has changed from Planning to Implement, which usually means the feature will be available in the near future.
Hi. It looks good workaround using HCL SafeLinx in front of Domino server. I am just thinking this below deployment for solving the problem of Domino IMAP not supporting TLS 1.3.
Currently the latest iPhone mail app. support just only TLS 1.3 in IMAP communication with mail servers but Domino mail server does not support TLS 1.3. So I am thinking how about putting SafeLinx server in front of Domino mail server.
