JavaMail 1.4.3 Failed @ ClientHello Phase (TLSv1)

Question

I've implemented this code below based on JavaMail 1.4.3 and successfully sent mails using Gmail and some other SMTP servers that enables SSL/TLS secured smtp protocal.
But when I try to run this code to send mail via mail.sgcc.com.cn, problems occured.
Here's the debug info:
init context
trigger seeding of SecureRandom
done seeding SecureRandom
%% No cached client session
ClientHello, TLSv1
RandomCookie:  GMT: 1282519260 bytes = { 97, 225, 120, 34, 21, 188, 197, 46, 157, 206, 150, 148, 176, 144, 171, 78, 155, 15, 174, 186, 120, 169, 151, 238, 178, 6, 185, 187 }
Session ID:  {}
Cipher Suites: [SSL_RSA_WITH_RC4_128_MD5, SSL_RSA_WITH_RC4_128_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_DES_CBC_SHA, SSL_DHE_RSA_WITH_DES_CBC_SHA, SSL_DHE_DSS_WITH_DES_CBC_SHA, SSL_RSA_EXPORT_WITH_RC4_40_MD5, SSL_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA, SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA]
Compression Methods: 
main, WRITE: TLSv1 Handshake, length = 73
main, handling exception: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
main, SEND TLSv1 ALERT:  fatal, description = unexpected_message
main, WRITE: TLSv1 Alert, length = 2
main, called closeSocket()
It seems that the connection failed at the ClientHello phase.
I don't know what has caused this failure.
Would you please give me some hits or suggestions?
Thanks in advance!

Answer 1

It seems that not too many people have noticed the missing results so far
Maybe this time it turns to be an advantage that the SDN forum seach is  - hmmm - not the best search in the world...
I used your post here to bump the issue, pointing to the growing public unrest...
In the discussion of Otto Gold's Blog "SCN infrastructure 2.0", Harald Boeing asked the question "But what value does SAP see in SCN?"  For me,  a quick fix of this issue would be a good sign for a high significance. (Or the other way round: I really wonder why you have to bump it at all.)
Rolf