Messaging 7, SSL Initialization Fails After Installing Solaris Patches
(Doc ID 1448959.1)
Last updated on APRIL 25, 2018
Applies to:Oracle Communications Messaging Server - Version 7.0.0 and later
Information in this document applies to any platform.
***Checked for relevance on 27-Jan-2014***
Messaging 7 patch 137204-12, with Solaris Crypto Framework (SCF).
After Solaris patches were applied on a Messaging Server system, the Messaging IMAP, POP, HTTP and SMTP SSL failed to start up.
Sample of POP proxy log:
20120302 201521 PopProxyAService.cfg Messaging Multiplexor (Sun Java(tm) System Messaging Server 7.3-12.01 (built Oct 15 2009)) started
20120302 201525 PopProxyAService.cfg (id 4) session start, client IP 188.8.131.52:43697, server IP 184.108.40.206:110
20120302 201555 PopProxyAService.cfg (id 52) SSL negotiation failed for IP 220.127.116.11: Cannot connect: SSL is disabled. (-12268)
Summarizing the conditions where this problem occurs:
- Messaging Server 7 running SSL with Solaris Crypto Framework / SSL hardware accelerator, and
- the user that starts up the Messaging Server (e.g. root) is not the same as the user that Messaging Server runs as (e.g. mailsrv), and
- Solaris 10 pkcs11 patch 144542-03 or later is applied.
Solaris patches were applied just before the problem started.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document