[
https://issues.apache.org/jira/browse/JAMES-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761798#comment-16761798
]
ASF GitHub Bot commented on JAMES-2657:
---------------------------------------
Github user mbaechler commented on the issue:
https://github.com/apache/james-project/pull/148
Ok, I understand your problem (and it's an interesting one, does that mean
you have a lot of users and domains on a single James instance ?).
You can probably put the common code into protocols/netty, WDYT ?
> SSLEngine and SslHandler unaware of remote ip and port
> ------------------------------------------------------
>
> Key: JAMES-2657
> URL: https://issues.apache.org/jira/browse/JAMES-2657
> Project: James Server
> Issue Type: Bug
> Reporter: Randymo
> Priority: Minor
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Our team uses the remote ip of the connect to determine the ssl cert we use
> for the connection. We had to make changes on our end to make that accessible
> to us at the level we needed it. It would be nice if James did this
> automatically itself.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
