Issue 3821 in k9mail: SSL handshake error
k9m...@googlecode.com
Owner: ----
Labels: Type-Defect Priority-Medium Product-k9mail
New issue 3821 by the.real...@gmail.com: SSL handshake error
http://code.google.com/p/k9mail/issues/detail?id=3821
What's going wrong?
Connecting to either POP or SMTP server failed due to SSL handshake error.
What steps will reproduce the problem?
* POP3 settings: TLS always on port 110, plain auth
* SMTP settings: TLS always on port 587, plain auth
What do you expect to have happen?
Get connection to server.
What do you see instead?
For POP server:
Certificate acceptance dialog with SSL handshake error. Re-appears while
trying to accept the certificate.
For SMTP server:
Runtime exception with RSA padding check error.
What version of K-9 are you using?
3.802
Is your email account a POP account, Exchange Account or an IMAP account?
POP3
What else should we know?
Connection to Email server works with standard Android Email client using
TLS with POP3 and SMTP.
Android v2.3.5
Attachments:
alogcat.2011-11-03-22-50-23+0100.txt 16.4 KB
k9m...@googlecode.com
Comment #1 on issue 3821 by bernhard...@gmail.com: SSL handshake error
http://code.google.com/p/k9mail/issues/detail?id=3821
you can try to set SSL (always), for some users this helped.
k9m...@googlecode.com
Comment #2 on issue 3821 by the.real...@gmail.com: SSL handshake error
http://code.google.com/p/k9mail/issues/detail?id=3821
Already tried, same result.
Only working option is plain transport layer.
k9m...@googlecode.com
Comment #3 on issue 3821 by bernhard...@gmail.com: SSL handshake error
http://code.google.com/p/k9mail/issues/detail?id=3821
why do you use pop3 with tls on port 110?
shouldn't u use port 995 for pop3s?
k9m...@googlecode.com
Comment #4 on issue 3821 by the.real...@gmail.com: SSL handshake error
http://code.google.com/p/k9mail/issues/detail?id=3821
The server accepts secure connection either on 110 or 995.
In K9 both ports lead to the above failure.
And as I already stated, communication with the server using TLS and the
same settings works with the standard Android Email client. Of course also
with a PC client.
k9m...@googlecode.com
Comment #5 on issue 3821 by bernhard...@gmail.com: SSL handshake error
http://code.google.com/p/k9mail/issues/detail?id=3821
do you use a custom cyanogenmod rom? Tracking this TLS related errors is
extremly difficult cause we can't reproduce them.
k9m...@googlecode.com
Comment #6 on issue 3821 by the.real...@gmail.com: SSL handshake error
http://code.google.com/p/k9mail/issues/detail?id=3821
Yes I use a custom ROM, UltraToxic v7.1.2 XWKI8.
k9m...@googlecode.com
Comment #7 on issue 3821 by kaeptn.h...@gmail.com: SSL handshake error
http://code.google.com/p/k9mail/issues/detail?id=3821
Similar problem here [Motorola Defy+, Android 2.3.6, K9 4.409]:
Account No1: working fine (no SSL/TLS)
Account No2: authentication errors (SMTP Port 465, POP Port 995, IMAP Port
993; SSL password plain)
I've tried deleting/recreating Account No2 several times, tripple-checking
all settings,but K9 never made one connection (neither pop, nor smtp, imap).
As a last resort I've installed MailDroid from the appstore and it works
just fine, on the first try. So I figure the problem must be somewhere with
K9...
Log-Excerpt see attachment. If someone would like to investigate further,
I can create a mailbox on the server for testing and provide you with the
details. Imho this should be a matter of high priority (i hate to leave k9!)
Attachments:
k9log.txt 22.9 KB
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
k9m...@googlecode.com
Comment #8 on issue 3821 by cketti: SSL handshake error
http://code.google.com/p/k9mail/issues/detail?id=3821
@kaeptn.haddock: That's not a similar problem at all. The log clearly
states it's an authentication error (wrong username/password).
It's possible that you enter the correct password but that it contains a
special character and K-9 Mail is using the wrong encoding when sending it
to the server. In any case, this is the wrong issue.
k9m...@googlecode.com
Comment #9 on issue 3821 by kaeptn.h...@gmail.com: SSL handshake error
http://code.google.com/p/k9mail/issues/detail?id=3821
ok thanks! I had figured that "handshake" = exchange of username and
password.
suppose I delete my comment here and open a new issue then.