Hello all!

I find some problem in OpenSSL when I use it for connecting to POP3s
(POP3 over SSL/TLS, port 995) server. When I use command "retr" it's
work fine. When I use "RETR" OpenSSL print some error.

Computer: Cel-633, RAM 192, HDD 10Gb
OS: WinXP SP2
OpenSSL: OpenSSL 0.9.8a 11 Oct 2005 (from openssl.org)
Compillers: MS VC 2003, MinGW (gcc version 3.4.2)

Look at this:

Servers: pop.yandex.ru or pop.pochta.ru

C:\test\openssl-0.9.8a\out32dll>openssl s_client -connect pop.yandex.ru:995
Loading 'screen' into random state - done
CONNECTED(00000744)

----8<-----
Some information about server cert
----8<-----

---
SSL handshake has read 1642 bytes and written 358 bytes
---
New, TLSv1/SSLv3, Cipher is DHE-RSA-AES256-SHA
Server public key is 1024 bit
Compression: NONE
Expansion: NONE
SSL-Session:
    Protocol  : TLSv1
    Cipher    : DHE-RSA-AES256-SHA
    Session-ID: 00570F483D85E1BF446C4B9FB05AD4DFF622702CFF3EDCB834551F11A51CEE38

    Session-ID-ctx:
    Master-Key: 6BC471ABF7CD222C4EADDE1D818B75CD08B9C827EE52F14BAD34B49F7CBD0D26
FE3B74B315223B94E7A58239C9C15FC9
    Key-Arg   : None
    Start Time: 1136465731
    Timeout   : 300 (sec)
    Verify return code: 21 (unable to verify the first certificate)
---
+OK POP Ya! v1.0na
user MyLogin
+OK password, please.
pass MyPass
+OK 7 message(s) 24062 bytes.
list
+OK 7 24062
1 5458
2 1853
3 9113
4 3125
5 1502
6 1500
7 1511
.
retr 2
+OK 1853 octets.
Received: from mxfront2.yandex.ru ([213.180.200.17]:25230 "EHLO
----8<-----
Header and mail.
It is works with "retr", but not work with "RETR"
----8<-----
.
RETR 2
RENEGOTIATING
1644:error:1409E0E5:SSL routines:SSL3_WRITE_BYTES:ssl handshake failure:.\ssl\s3
_pkt.c:534:


I'm just use "RETR" (like in RFC) command instead of "retr"...


---
With best regards,
Denis.




______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [email protected]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to