On Tuesday, 20 February 2024, at 10:45 AM, cyrus wrote:
Perhaps try and delete your tls_sessions.db file (after stopping cyrus master) and then restart it.
Sorry, I cannot test this option: it is a production cluster, and we used the very first effective fix. However, I doubt that it could help; the issue happened at second connection only, when tls_sessions database already has fresh fingerprint from this client.
Settingg number of concurrent connections to one at client side fixed the issue too. By default Thunderbird uses 3 or 5 connections to server to improve performance.
