Hi Jan,
I would check to make sure the unlimited strength policy files are installed.
Link to Java 7 policy files below:
http://www.oracle.com/technetwork/java/javase/downloads/jce-7-download-432124.html
Kind regards,
Johnny Minty
Sent from my Windows Phone
Thanks for this. No dice. -showcerts doesn't display any certs
associated with the connection. How very odd...
Jan
On 10/15/13 11:09 PM, Johnny Minty joh...@minty.net.nz wrote:
Hi Jan,
I would check to make sure the unlimited strength policy files are
installed.
Link to Java 7 policy
Hmm. You alluded to the keytool command in the install docs holding for
James v 2.3, which I take it is what you are running. Maybe the server
doesn't like the wildcard cert. If this is a self-signed cert, try
generating a new one for just the domain you need for the mail server and
see if the
Thanks, Robert. I'm a bit leary about stability of V3 yet and haven't
done any testing to see if my custom mailets will operate the same way
they do in V2.3 -- any insight there would be helpful.
I will take your advice and regenerate the certificates. I'm currently
testing with a self-signed
Well, one problem down, one to go?
TLS Connectivity now checks out at the openssl and nmap levels. I even
get:
No client certificate CA names sent
---
SSL handshake has read 1666 bytes and written 278 bytes
---
New, TLSv1/SSLv3, Cipher is DHE-RSA-AES256-SHA
Server public key is 2048 bit
Secure
Curiouser and curiouser...
Openssl connection testing works and I can ehlo and send email to the
server using that.
Exchange server connects to james and then hangs no matter what I do.
Anybody ever gotten an exchange 2010 server to communicate via tls and
basic auth with james 2.3?
Jan
On
Okay... I think I may have found it and, if I'm right, it isn't pretty.
With UseTLS enabled on an smtpserver in james 2.3 it looks like the
following is true:
- it doesn't advertise starttls and expects TLS to have been initiated as
part of the initial connection to, say, port 465
- it doesn't
