Fritz, Thanks for the clarification. I am only using another port 465/587 because local isps block 25, not exclusively for TLS/SSL.
By the way, I am still very much stuck. Any idea what is happening and why I'm getting the timeout errors in maillog.txt? Nov-27-11 12:02:38 [Worker_1] Error: Worker_1 accept to client failed IO::Socket::SSL=GLOB(0xde8dc48) (timeout: 180 s) : Connection timed out On Nov 27, 2011, at 3:32 AM, Fritz Borgstedt wrote: > For Users of ASSP <[email protected]> schreibt: >> Thanks for your response Doug. Your point is take about port 465. I >> have tried 587 and of course there is no difference in behavior. >> I'll repost my question in the test list. > > > > IMHO he meant that SSL over a dedicated port is old fashioned. > listenPortSSL is meant for SSL only. > > The standard TLS connection can be set up over any listenport, for > example with listenPort2 set to 587. > DoTLS must be set to "do TLS". > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Assp-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/assp-user ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
