1. The
<sockets>
<server-sockets>
<factory name="ssl" ...>
<keystore>
</keystore>
</factory>
</server-sockets>
</sockets>hierarchy must become
<sockets>
<server-sockets>
<factory name="ssl" ...>
<ssl-factory>
<keystore>
</keystore>
</ssl-factory>
</factory>
</server-sockets>
</sockets>2. A new <key-password>xxx</key-password> element must be added inside the <keystore>...</keystore> block in addition to the <password>xxx</password> *even if the private key password is the same as the keystore password*.
Everything seems to work quite well in my pretty complex configuration; next week I will put v3 in production and monitor it carefully for a few days, and then let you know.
I will also update james-config.xml in trunk and the wiki page for ssl support.
Vincenzo
[EMAIL PROTECTED] wrote:
Would you mind terribly taking a short pause in your coding, and just test?
First tests working. The only problem is a warning at startup: data-sources in config.xml is deprecated. I removed the data-sources entry leaving only the data-source tag and the warning disappeared.
I am running on very limited time right now, and just want a good sanity check before I replace the trunk.
My binary mailet wasn't working. I had to recompile my matcher/mailets against the latest james/mailet api and compile against cornerstone-store-api-1.0 instead of the old cornerstone.jar from james 2.2 I also replaced "Component" with "Service" in some of my mailets.
It all seems to work like before.
Stefano
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
