We use LTPA Token authentication inside company for HCL Sametime 12.0.2. It was working fine. When Sametime 12.0.2FP1 arrived we upgraded our Sametime and Notes 14 clients were unable to login with LTPA. Only regular password login was working. Sametime Authentication container logs brought us the following: error: Error decoding LtpaToken2: "error:1C800064:Provider routines::bad decrypt". Trying as v1: false
[2024/08/23 13:39:41] info: ::ffff:172.22.0.8 - - We opened case and support mentioned that: in HCL Sametime 12.0.2 FP1 we disabled LTPA V1 token support by default - in favor of LTPA V2 which is more secure. The Embedded clients, especially the 'older' ones still present only the LTPA V1 tokens. In Domino SSO document, our configuration was LtpaToken and LTPAToken2. We changed format of token to "LTPAToken2 only" and did restart of Domino and this has resolved issue.

I was working in one environment which had average spam rating and many emails that this eligible company sent have not reached intended destination. Colleague of mine suggested my a site Mail-tester.com. idea is simple, you sent a mail and gives you score how to improve. long story short, after some time we improved from 6 to 10 from maximum 10 possible. Free version allow 4 mails per day which might be sufficient if you dont do too many changes per day.

While ago during 12.0 we faced issue that after upgrade to V12.0 Notes was able to work with our VPN server. Error message pointed to very low TCPIP level. and today my colleagues Stanislav Schvachko has found, that issue is finally resolved. Just enable Notes.ini parameter Network_Resiliency=0 , that will disable new V12 feature

Updated MAIL 12.0.1 Template to address some issues One of my customers noticed that when they join meeting, URL or Online meeting is LowerCased. as result also password is lowercased and people fail to join. I opened ticked and very fast HCL did changes to template https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0097354

If you have ACL ACTION "MODIFY ALL NAMES FIELDS, OR READERS AUTHORS FIELDS" then upon user rename, user is renamed by adminp in names fields and security fields. Drawback is when user is leaving company and admin deletes user, if you have this setting enabled, then user will be deleted from all Names fields or Readers/Authors fields. Which may lead to strange documents, like Approved by "Empty string", because person who approved left company and adminp deleted him from field. Which is not ok, since breaks logic and compliance, we have to know who accepted document.

One way to improve HTTP application is to cache different objects, like CSS, JPG , .JS files. To do so you must create a HTTP Header rule. I always do this when improve performance of HTTP, but in v11 I tried and I got error message, that "Expiration days is required"