> >Alrighty, then. Apache james V2.3 tls support is apparently not >compatible with microsoft exchange handling of tls connection management >since james v2.3 doesn't support starttls.
Next, I went for trying apache james 3 beta 4 and... Voila! It supports starttls so I get a connection. ...only to find that I get an exception and find that james 3 beta 4 isn't rfc compliant, per: https://issues.apache.org/jira/browse/JAMES-1422 ...now, that was... July of 2012... https://issues.apache.org/jira/browse/JAMES-1422 Although it was referenced, I can't seem to find a beta 5 and the issue above is still unresolved. I am now trying to find the "snapshot" for this fix that apparently went into trunk at some point. Am I the only person trying to use apache james with tls and exchange? Thanks for all the help and support. Jan --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
