[
https://issues.apache.org/jira/browse/JAMES-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730150#comment-16730150
]
Tellier Benoit commented on JAMES-2631:
---------------------------------------
Clearly `james.mailetcontext | Could not convert socket to TLS` is the
incriminated log though I must admit this is too little information for me to
understand what is going on.
Could you give a try to the James 3.2.0 ? We did rework mailet logging, thus I
will at the very least have the class name....
> TLS 1.2 problems with Certificate Request
> -----------------------------------------
>
> Key: JAMES-2631
> URL: https://issues.apache.org/jira/browse/JAMES-2631
> Project: James Server
> Issue Type: Bug
> Affects Versions: 3.0.1
> Reporter: Arnau Rebassa
> Priority: Major
> Attachments: james_response.png, server_request.png
>
>
> We are using james 3.0.1 configured to use TLS in remote deliveries. The
> sending of emails over TLS is working fine but we have problems sending
> emails to a particular server which performs a "Certificate Request". When
> this happens, in a tcpdump capture I can see that, James returns an error
> Alert (Level: Fatal, Description: Certificate Unknown).
>
> The certificate used by the remote server is issued by a well know CA. In the
> picture server_request.png you can see as the remote server requests a
> "Certificate request" to the client (in this case to James).
>
> In the file james_reponse.png you can see how James sends a Fatal alert.
>
> I have been looking into the documentation but I haven't found the way to
> specify a keystore in the mailetcontainer.xml. Is this possible? Anyone knows
> how to fix this?
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
