My wildcard SSL certificate works for the webmail site in IIS. But it does not work for SMTP and IMAP.
I have followed the SSL configuration instructions in the manual as well as http://www.mailenable.com/kb/Content/Ar ... D=me020479 to no avail.
Here is some output from the SMTP debug log:
Code: Select all
05/18/12 11:16:56 ME-I0082: Service binding to all addresses on port (25) for IPv4 family (2). Requires authentication 0
05/18/12 11:16:56 ME-I0085: Service (Alternate) binding to all IPv4 addresses on port (465). Requires authentication 1
05/18/12 11:16:56 ME-IXXXX: Initalised Recv Message Master Thread
05/18/12 11:16:56 ME-I0076: Listening for connections
05/18/12 11:16:56 ME-I0144: Service Completed Loading Agents
05/18/12 11:16:56 ME-IXXXX: Initalised Recv Message Master Thread
05/18/12 11:16:56 Permissions error opening the certificate store. Inbound SSL will fail unless this service has permissions to the store. See http://www.mailenable.com/kb/Content/Article.asp?ID=me020479
05/18/12 11:16:56 **** Error creating credentials object for SSL session
05/18/12 11:16:56 Unable to locate or bind to certificate with name "*.mydomain.com"
05/18/12 11:16:56 ME-I0076: Listening for connections
When trying to connect to SMTP/SSL from gmail, it reports the following server error: Server response: 454 TLS not available due to temporary reason code(454)
Is my wildcard certificate the problem here? Does MailEnable not have the ability to use wildcard certificates for SMTP and IMAP?
In the meantime, I'll retrace the steps for configuring permissions on the certificate in case I've missed something.
Thanks for your help!