------------ Original Message ------------ > Date: Wednesday, October 01, 2014 07:40:38 +1000 > From: Voytek <[email protected]> > To: [email protected] > Cc: > Subject: Re: [k-9-mail] Re: Latest update has broken outbound SMTP SSL/TLS connections - completely > > > > On 1 October 2014 7:07:17 am AEST, Tim O'Connor > <[email protected]> wrote: >> What a mess! The app has worked well up until the last update. >> Now it's >> >> unusable due to the SSL certificate bug. Like others mentioned, it >> doesn't >> matter what type of authentication I choose, nothing works! >> >> I have mail accounts on other servers using SSL and those were >> fine. My >> >> problem is with IMAP.secureserver.net at GoDaddy and their SMTP >> server. I >> have managed to limp along by deleting the offending account and >> re-adding >> it... But it still throws SSL errors in the K9mail-errors folder >> on every >> polling session but I have been able to send a few mails, but >> doesn't inspire a lot of confidence. If I have to babysit my >> email outbox, I will >> have to consider another app. That sux. >> > > What facilities does your smtp server offer? > > If you telnet to your mail host on relevant port, and, 'ehlo email > address' you should see what should be used. > If you are using what's being offered, maybe there is a bug, but, > I don't see that here, ymmv > > u0_a138@hammerhead:/ $ telnet mailhost 25 > 220 ESMTP Postfix > ehlo [email protected] > 250-PIPELINING > 250-SIZE 20971520 > 250-ETRN > 250-STARTTLS > 250-AUTH PLAIN LOGIN > 250-AUTH=PLAIN LOGIN > 250-ENHANCEDSTATUSCODES > 250-8BITMIME > 250 DSN > quit > 221 2.0.0 Bye > Connection closed by foreign host > > 1|u0_a138@hammerhead:/ $ telnet mailhost 587 > 220 ESMTP Postfix > ehlo [email protected] > 250-PIPELINING > 250-SIZE 20971520 > 250-ETRN > 250-STARTTLS > 250-ENHANCEDSTATUSCODES > 250-8BITMIME > 250 DSN > quit > 221 2.0.0 Bye > Connection closed by foreign host
I looked at the IMAP.secureserver.net server referenced above. While it claims to support STARTTLS, it and K-9 5.0 don't seem to get along when STARTTLS is selected as the K-9 "incoming server" security setting. That server is running Courier-IMAP which I don't use, so I can't easily muck with things to tell if this is general Courier issue, a secureserver.net configuration problem or something that K-9 isn't doing quite right. Testing against Dovecot IMAP servers, things seem fine (both with STARTTLS and SSL/TLS). When reporting problems with receiving mail it might be useful to include the full name of the mail server in question, in addition to the protocol, security, port and authentication your client is configured to use. [Do NOT include usernames or passwords]. For sending mail problems, the same applies (though protocol is a given). Except for private and corporate servers, I don't see any privacy or security issues with including the full mail server name, or the other details. [there isn't really with private or corporate servers, but a certain amount of paranoia tends to reign in those environments.] I think that with some specific details the developers will be able to address things. Simply saying that it doesn't work isn't very useful. There are a range of commonly used IMAP/POP/sendmail servers and numerous ways to configure them, so having specifics should help narrow down where the problems are. [personally, i have had no issues with K-9 5.0 against my Dovecot IMAP/Sendmail ssl/tls configurations.] - Richard -- -- You received this message because you are subscribed to the K-9 Mail Users List. To post to this group, send email to [email protected] To unsubscribe, email [email protected] To report an issue with K-9 Mail, visit http://code.google.com/p/k9mail/issues/list For more options, visit this group at http://groups.google.com/group/k-9-mail --- You received this message because you are subscribed to the Google Groups "K-9 Mail" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
