I have tried in the past and given up on implementing "doTLS" on a Windows Server 2008 x64 box and have settled on "TLS to Proxy" which has been working just fine for many months. Recently we have been getting more spam through TLS and now I want to revisit "doTLS" and see if I can find what is wrong. The problem with "doTLS" for us has been it fails with the following listed in the ASSP log file with a windows that pops up that reads "Perl Command Line Interpreter has stopped working": DEBUG: .../IO/Socket/SSL.pm:1471: new ctx 495621816 DEBUG: .../IO/Socket/SSL.pm:938: start handshake DEBUG: .../IO/Socket/SSL.pm:505: starting sslifying DEBUG: .../IO/Socket/SSL.pm:545: Net::SSLeay::accept -> -1
I am using the cert files(.pem) that come with ASSP I have also installed OpenSSL to create these files. I also removed the .pem files and had ASSP create them but still have the failures. All mail traffic is through port 25. When I am testing the TLS I am using OpenSSL on my workstation with the following command which works fine when "TLS to Proxy" is set but "doTLS" does not. openssl s_client -connect 10.0.0.1:25 -starttls smtp The client does report an error listed below: 2036:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake failure:.\ssl\s23_lib.c:184: I am not sure what to check next. Has anyone successfully implemented TLS on their Windows Server? Did I missing something during the install like extra files that need to be installed(all the perl modules are currently enabled and working in ASSP)? Thanks for any help. Dan ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
