Session cacheing is never useful, as we use a new context for every TLS startup.
However, removing the support triggers odd behaviour from Outlook Express (only
when there is an IMAP server on the same machine as Exim): an initial connect
from the OE client fails, the immediate retry works.
Previously it was possible to log spurious information in receive log
lines.
Previously it was possible to log spurious information in receive log
lines.
+JH/37 Bug 2255: Revert the disable of the OpenSSL session caching. This
+ triggered odd behaviour from Outlook Express clients.
+
Exim version 4.90
-----------------
Exim version 4.90
-----------------
else
DEBUG(D_tls) debug_printf("no SSL CTX options to set\n");
else
DEBUG(D_tls) debug_printf("no SSL CTX options to set\n");
-/* Disable session cache unconditionally */
-
+/* We'd like to disable session cache unconditionally, but foolish Outlook
+Express clients then give up the first TLS connection and make a second one
+(which works). Only when there is an IMAP service on the same machine.
+Presumably OE is trying to use the cache for A on B. Leave it enabled for
+now, until we work out a decent way of presenting control to the config. It
+will never be used because we use a new context every time. */
+#ifdef notdef
(void) SSL_CTX_set_session_cache_mode(ctx, SSL_SESS_CACHE_OFF);
(void) SSL_CTX_set_session_cache_mode(ctx, SSL_SESS_CACHE_OFF);
/* Initialize with DH parameters if supplied */
/* Initialize ECDH temp key parameter selection */
/* Initialize with DH parameters if supplied */
/* Initialize ECDH temp key parameter selection */