Fritz Borgstedt wrote: > ASSP development mailing list <assp-test@lists.sourceforge.net> > schreibt: > >> Ok - that worked. I can now connect using SSL (not TLS) from my >> client >> (Thunderbird) to ASSP, and ASSP successfully connects to Postfix >> without >> using SSL/TLS. >> > > I guess you put 465 into listenPortSSL and you connect to port 465 via > Thunderbird. > That forces a SSL session - because listenPortSSL understands only SSL. > > If you put 465 into listenPort2 (or listenPort) it will be TLS/SSL > according to the client request. > eg: "587|465". > Postfix configuration - Port 10024 - no TLS/SSL supported Port 10025 - TLS supported (postfix option smtpd_tls_security_level=may) Port 10026 - SSL supported (postfix option smtpd_tls_wrappermode=yes)
with the following ASSP settings - listenPort:=25 smtpDestination:=10024 listenPort2:=587 smtpDestination:=10025 listenPortSSL:=465 smtpDestinationSSL:=10026 Only successful communication is via port 25. with - smtpAuthServer:=10024 Connecting to 587 works with no encryption (same as 25). with - smtpDestinationSSL:= Connecting to 465 via Thunderbird+SSL works. No combination appears to support TLS mode from Thunderbird. No combination appears to support TLS/SSL communications between ASSP & Postfix - I see Postfix errors regarding protocol version. -- Daniel ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test