Viktor, Thanks for getting back to me.
> The resumption problem can be worked around by setting the server-side > session cache database empty (the default setting): > > smtpd_tls_session_cache_database > > This is the recommended setting, since clients should be using session > tickets instead. After reviewing the setting you provided here, I think I figured out the issue, this was set to store session cache in a local DB which wasn’t storing session tickets across the cluster. This was causing a client to connect on one server, then switch to the other and produce a fatal error (which didn’t really make anything unusable). After correcting this and monitoring for the issue it’s finally gone away. Best regards, Tom
smime.p7s
Description: S/MIME cryptographic signature
