A few observations, please help me make sense of them if you can. I have not made any changes to the security settings of my jdk 1.4.2 that should affect this.
When running the TestCmdSTARTTLS unit test it seems to work, and with a bit of logging in place the new socket actually gets created. Why does the call to SSLSocketFactory.getDefault() work when running the test and not when running within JBoss? I have been using SSL with JBoss-Jetty and JBoss-Tomcat for ages, and I was able to call SSLServerSocketFactory.getDefault() fine from CmdSTARTTLS both when running as a test and when running within JBoss. I am wondering if maybe it could be due to me being outside the US? I am not sure though, because then I think the test should have failed too. Could one of you Amricans try this out and see what results you get? You have to add the following line to the SMTPProtocol mbean in jboss-service.xml of the project to enable TLS: tls-enabledtrue Then use telnet and see what happens: 220 badmojo.superlinksoftware.com SMTP Server (JBMAIL SMTP Server version 0.1) ready 26 March 2004 15:31:00 CET EHLO localhost 250-badmojo.superlinksoftware.com Hello localhost (127.0.0.1 (127.0.0.1)) 250-STARTTLS 250 AUTH LOGIN PLAIN STARTTLS Cheers, Kab <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3827607#3827607";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3827607>Reply to the post</a> ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
