Yes, I can see clearly in my server logs that up until the V5 update (my logs go back that far) that I was connecting to port 465, authenticating (via SSL), and going on my merry way. I can also see in those same logs where it stopped working. I see connections to the port, then the connection immediately drops due to failed authentication. Funny thing. Now that I've gone to the trouble of converting back to the stock Android email client, everything is again functional. No server configuration changes or account setting changes required. Imagine that.
Here's the thing. Email is not a "toy" for me. It's a utility, one that I expect to work. I don't have the time or even the inclination to spend hours or days "fiddling" with new settings just because some developer decided it was a good idea to make a change to something that had previously been working. Apparently, one or more of the following statements are true: * The K9 development team thinks they're working for Apple and that means they think they're qualified to make users' decisions about what their customers "should have" instead of listening to what their customers tell them they want. * K9 is more interested in experimentation than they are in providing a reliable product. * K9's testing regimen is insufficient to detect problems that their changes introduce into the code base before release. * K9 lacks the will (or the integrity) to admit when they've made a mistake and to back out a change that has introduced an obviously disruptive defect. * K9 thinks they are the center of the universe and as such, are well within their right to expect their users to be willing to upend everything about their system configurations just to adapt to whatever changes K9 chooses to unleash on them. I'm not interested in hearing any more suggestions about configuration changes that I might 'try' in order to fix K9's problem. I've already fixed it - by ditching K9. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Richard Sent: Wednesday, October 01, 2014 7:59 PM To: [email protected] Subject: Re: [k-9-mail] Re: Latest update has broken outbound SMTP SSL/TLS connections - completely ------------ Original Message ------------ > Date: Thursday, October 02, 2014 10:35:11 +1000 > From: Voytek <[email protected]> > To: [email protected] > Subject: Re: [k-9-mail] Re: Latest update has broken outbound SMTP SSL/TLS connections - completely > > > > On 1 October 2014 11:21:05 pm AEST, Robert Garrett <[email protected]> > wrote: >> Here are the significant points: >> 1) My email server, which I own and am in complete control of > >> So, K9 is the only thing that has changed, and now K9 is the only >> email client that won't work. Doesn't that make it pretty obvious >> where the defect lies? > > Yes, no, maybe. > Perhaps, for sure, no way. > > Choose one, choose more than one, choose all that apply > > You own all the pieces, mail client, mail server, produce the > evidence. > > Maybe you are right, maybe you are wrong, without the logs, you are > wasting your time, and, developers time, shooting moving target can be > fun, but, hardly a productive pastime. > >> SSL/TLS and 465 (out) > > On a separate note, I'm far from a mail expert, and, am happy to be > corrected, but, I was under impression that port 465 for smtp had been > deprecated since...late 90ies?, and, submission port 587 is the > preferred and appropriate port? > Port 465 is what is used if you're using ssl/tls. If you're going with starttls it's 587. There are those who prefer starttls/587 (and yes, technically 465 is depreciated), but not all clients support that. Google/gmail's submission settings are ssl/tls port 465 -- see: <https://support.google.com/mail/troubleshooter/1668960?hl=en> (you'll have to make selections, e.g., imap/android (with javascript on) to see the final settings page.) The problem that I see with starttls is that if you don't set your client to require it (and rather take an "if available" option) you don't really know if your connection is encrypted (unless you're running the server). K-9 dropped the "if available" option for starttls with the recent update so anyone who was previously using the K-9 "starttls - if available" setting and is now having problems should probably select "none" as I suspect their server wasn't/isn't really doing starttls. - 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. -- -- 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.
