> > openssl s_client -CApath /etc/certificates -starttls smtp -connect
mail.mydomain.com:465
>However, using openssl to test the connection yields a similar result:
Yes, using wrong options will result in simlar wrong results!
Port 465 is a SSL listener - what should '-starttls' do with it ? First
think about what a SSL listener is, what 'STARTTLS' is doing and when it
is used and how it works (if unclear read RFC's) - than use :
> openssl s_client -starttls smtp -connect mail.mydomain.com:25
or
> openssl s_client -connect mail.mydomain.com:465
Thomas
Von: Jason Horn <jason.w.horn@...>
An: ASSP development mailing list <assp-test@...>
Datum: 27.11.2011 18:04
Betreff: Re: [Assp-test] Antwort: Re: ASSP V2 SSL submission over
port 465/587 not working
Thomas,
Thanks for that. It seems obvious now that I think of it. However, using
openssl to test the connection yields a similar result:
> openssl s_client -CApath /etc/certificates -starttls smtp -connect
mail.mydomain.com:465
CONNECTED(00000003)
the server does not respond to any commands typed at this point
In maillog.txt, I get many of these messages:
Nov-27-11 11:45:36 [Main_Thread] Info: unable to detect any running worker
for a new connection - wait
Nov-27-11 11:45:36 [Main_Thread] Info: unable to detect any running worker
for a new connection - wait
Nov-27-11 11:45:36 [Main_Thread] Info: unable to detect any running worker
for a new connection - wait
Nov-27-11 11:45:36 [Main_Thread] Info: unable to detect any running worker
for a new connection - wait
Then I get:
Nov-27-11 11:59:37 [Worker_1] Error: Worker_1 accept to client failed
IO::Socket::SSL=GLOB(0xdc23bf0) (timeout: 180 s) : Resource temporarily
unavailable
Nov-27-11 11:59:40 [Worker_10000] Info: saving Stats in file asspstats.sav
Nov-27-11 12:00:05 [Worker_10000] Info: hourly scheduler running at 12:00
Nov-27-11 12:00:08 [Worker_2] Error: Worker_2 accept to client failed
IO::Socket::SSL=GLOB(0xb43767e8) (timeout: 180 s) : Connection timed out
Nov-27-11 12:00:39 [Worker_3] Error: Worker_3 accept to client failed
IO::Socket::SSL=GLOB(0xec8a018) (timeout: 180 s) : Connection timed out
Nov-27-11 12:01:11 [Worker_4] Error: Worker_4 accept to client failed
IO::Socket::SSL=GLOB(0xb19f30e8) (timeout: 180 s) : Connection timed out
On Nov 27, 2011, at 2:48 AM, Thomas Eckardt wrote:
> 'telnet' can't do SSL - use openssl.
>
> Thomas
>
>
>
>
> Von: Jason Horn <jason.w.horn@...>
> An: ASSP development mailing list <assp-test@...>
> Datum: 27.11.2011 03:37
> Betreff: Re: [Assp-test] ASSP V2 SSL submission over port 465/587
> not working
>
>
>
>
> Doug,
>
> Some more information: If I telnet over to port 465, I the "connected"
> message, but no response to commands. If I input something, then hit
> return, I get no response. If I do this three times consecutively, the
> connection will close with "Connection closed by foreign host." In
> maillog.txt I get this error:
>
> Nov-26-11 21:18:07 [Worker_1] Error: Worker_1 accept to client failed
> IO::Socket::SSL=GLOB(0xf287260) (timeout: 180 s) :
>
>
> If I telnet in and do nothing, It will stay connected, but after 2 min
30
> sec, I get may copies of this error:
>
> Nov-26-11 21:24:18 [Main_Thread] Info: unable to detect any running
worker
> for a new connection - wait
> Nov-26-11 21:24:18 [Main_Thread] Info: unable to detect any running
worker
> for a new connection - wait
> Nov-26-11 21:24:18 [Main_Thread] Info: unable to detect any running
worker
> for a new connection - wait
> Nov-26-11 21:24:18 [Main_Thread] Info: unable to detect any running
worker
> for a new connection - wait
> Nov-26-11 21:24:18 [Main_Thread] Info: unable to detect any running
worker
> for a new connection - wait
> Nov-26-11 21:24:18 [Main_Thread] Info: unable to detect any running
worker
> for a new connection - wait
>
> Then at 3 min I get these erors:
>
> Nov-26-11 21:24:18 [Worker_1] Error: Worker_1 accept to client failed
> IO::Socket::SSL=GLOB(0xf287dd0) (timeout: 180 s) : Resource temporarily
> unavailable
> Nov-26-11 21:24:49 [Worker_2] Error: Worker_2 accept to client failed
> IO::Socket::SSL=GLOB(0xb32c7048) (timeout: 180 s) : Connection timed out
> Nov-26-11 21:25:20 [Worker_3] Error: Worker_3 accept to client failed
> IO::Socket::SSL=GLOB(0xd600208) (timeout: 180 s) : Connection timed out
> Nov-26-11 21:25:51 [Worker_4] Error: Worker_4 accept to client failed
> IO::Socket::SSL=GLOB(0xb07a5ee8) (timeout: 180 s) : Connection timed out
> Nov-26-11 21:26:23 [Worker_5] Error: Worker_5 accept to client failed
> IO::Socket::SSL=GLOB(0xe8470c0) (timeout: 180 s) : Connection timed out
>
> An the pattern above repeats indefinitely.
>
>
>
>
>
>
>
> On Nov 26, 2011, at 7:42 PM, Doug Lytle wrote:
>
>>
>> Jason Horn wrote:
>>> If I telnet over to port 465, I get a "Connected to" message, but
> nothing else. It seems like ASSP can't communicate with postfix, and
there
> is no response from postfix from any command issued.
>>
>> For the initial testing, eliminate the SSL portion of it. Once you
have
>
>> that working, then add it back.
>>
>> Do you get any connection with just the normal telnet localhost 25?
>>
>> Doug
>>
>>
>>
>
------------------------------------------------------------------------------
>> 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-test mailing list
>> Assp-test@...
>> https://lists.sourceforge.net/lists/listinfo/assp-test
>
>
>
------------------------------------------------------------------------------
> 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-test mailing list
> Assp-test@...
> https://lists.sourceforge.net/lists/listinfo/assp-test
>
>
>
>
> DISCLAIMER:
> *******************************************************
> This email and any files transmitted with it may be confidential,
legally
> privileged and protected in law and are intended solely for the use of
the
>
> individual to whom it is addressed.
> This email was multiple times scanned for viruses. There should be no
> known virus in this email!
> *******************************************************
>
>
>
------------------------------------------------------------------------------
> 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-test mailing list
> Assp-test@...
> https://lists.sourceforge.net/lists/listinfo/assp-test
------------------------------------------------------------------------------
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-test mailing list
Assp-test@...
https://lists.sourceforge.net/lists/listinfo/assp-test
DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally
privileged and protected in law and are intended solely for the use of the
individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no
known virus in this email!
*******************************************************
|