[stunnel-users] Windows Live Mail issue ?

Thu Jan 19 01:02:08 CET 2012

Victor;

I can't speak to your peer disconnection issue, but the byte counts pretty
much mirror what I see from day-to-day.  I looked in the documentation
to see if I could find out how the byte counts are generated, but I was
unsuccessful. In any case, here are the last 3 closures from my log:

2012.01.18 17:40:09 LOG6[320:3332]: SSL_shutdown successfully sent 
close_notify alert
2012.01.18 17:40:09 LOG5[320:3332]: Connection closed: 1526 bytes sent 
to SSL, 24149 bytes sent to socket
2012.01.18 17:40:50 LOG6[320:2688]: SSL_shutdown successfully sent 
close_notify alert
2012.01.18 17:40:50 LOG5[320:2688]: Connection closed: 126 bytes sent to 
SSL, 2797 bytes sent to socket
2012.01.18 17:50:36 LOG6[320:3412]: SSL_shutdown successfully sent 
close_notify alert
2012.01.18 17:50:36 LOG5[320:3412]: Connection closed: 1270 bytes sent 
to SSL, 121955 bytes sent to socket

Regards,

Thomas

On 1/18/2012 1:38 PM, Victor wrote:
> I'm new with stunnel and I'm experiencing a issue. Windows Live Mail 
> is closing the connection with the SSL tunnel without send the close 
> down packet, resulting in connection reset by peer. Follow the output 
> debug of stunnel:
>
> 2012.01.18 17:13:25 LOG7[16954:34377572800]: Socket closed on read
> 2012.01.18 17:13:25 LOG7[16954:34377572800]: Sending SSL write shutdown
> 2012.01.18 17:13:25 LOG7[16954:34377572800]: SSL alert (write): warning:
> close notify
> 2012.01.18 17:13:25 LOG6[16954:34377572800]: SSL_shutdown successfully 
> sent
> close_notify
> 2012.01.18 17:13:25 LOG3[16954:34377572800]: SSL_read: Connection 
> reset by
> peer (54)
> 2012.01.18 17:13:25 LOG5[16954:34377572800]: Connection reset: 293 bytes
> sent to SSL, 1293 bytes sent to socket
> 2012.01.18 17:13:25 LOG7[16954:34377572800]: Service stunnel finished (0
> left)
> 2012.01.18 17:13:25 LOG7[16954:34377572800]: str_stats: 28 block(s), 988
> byte(s)
>
> The e-mail message is sent successfully but Im very intrigued with the 
> line
> "Connection reset: 293 bytes sent to SSL, 1293 bytes sent to socket", 
> that
> make me think that some data was lost in the middle of the connection. I
> need to fix something or this is a normal behavior ?