Письмо отправляется и приходит к клиенту, но подозрительно в логе stunnel. popa3d+stunnel - в логах stunnel в правильном примере: 2004.12.04 22:40:02 LOG7[2406:134600704]: pop3s connecting 127.0.0.1:110 2004.12.04 22:40:02 LOG7[2406:134600704]: Remote FD=12 initialized 2004.12.04 22:40:02 LOG7[2406:134600704]: Socket closed on read 2004.12.04 22:40:02 LOG7[2406:134600704]: SSL alert (write): warning: close notify 2004.12.04 22:40:02 LOG7[2406:134600704]: SSL write shutdown (output buffer empty) 2004.12.04 22:40:02 LOG7[2406:134600704]: SSL alert (read): warning: close notify 2004.12.04 22:40:02 LOG7[2406:134600704]: SSL closed on SSL_read 2004.12.04 22:40:02 LOG7[2406:134600704]: Socket write shutdown (output buffer empty) 2004.12.04 22:40:02 LOG5[2406:134600704]: Connection closed: 12678 bytes sent to SSL, 10178 bytes sent to socket 2004.12.04 22:40:02 LOG7[2406:134600704]: pop3s finished (0 left)
В моём случае почему-то отсутствует SSL alert (read): warning: close notify и SSL closed on SSL_read а присутствует SSL socket closed on SSL_read: 2006.08.07 14:45:41 LOG7[269:135391232]: FD 10 in non-blocking mode 2006.08.07 14:45:41 LOG7[269:135391232]: pop3s connecting 127.0.0.1:110 2006.08.07 14:45:41 LOG7[269:135391232]: Remote FD=10 initialized 2006.08.07 14:45:42 LOG7[269:135391232]: Socket closed on read 2006.08.07 14:45:42 LOG7[269:135391232]: SSL alert (write): warning: close notify 2006.08.07 14:45:42 LOG7[269:135391232]: SSL write shutdown (output buffer empty) 2006.08.07 14:45:42 LOG7[269:135391232]: SSL socket closed on SSL_read 2006.08.07 14:45:42 LOG5[269:135391232]: Connection closed: 8852 bytes sent to SSL, 55 bytes sent to socket 2006.08.07 14:45:42 LOG7[269:135391232]: pop3s finished (0 left) и почему-то если понизить ур-нь дебага в stunnel.cnf -> debug = 3 то в логе 2006.08.07 11:59:51 LOG3[292:135391232]: SSL_read (SSL_ERROR_SYSCALL): Connection reset by peer (54) Из-за чего это может происходить? Заранее спс. Вячеслав -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]