I’ve used the K9 5.6* from the project’s development archive, but ended up moving on to the Open Mail 5.6 K9 fork, as the developer did do a few things on it to stabilise things.
I’ve communicated with the developer of the Open Mail 5.6 K9 fork.
He seems a really decent guy, kind hearted even.
He says that he does not intend to do anything to the Open Mail 5.6 K9 fork that would destabilise anything, in fact he intends at the moment to keep it unchanged as he is very busy with other things.
I think while using it, I have had to refresh/restore the downloaded emails occasionally, but my phone’s sdcard is getting full, so what that is indicative of I can not say for sure.
(An sdcard getting full, is a known issue with a number of other apps anyway.)
But, if you’re using IMAP or like, from time to time you could do a forced refresh (by pulling your finger down from the top of the folder’s listed email window) of Sent emails, and any other important mail folder you have created through your mail application on your PC or bigger device.
(This vintage of K9 and forks does not let you create new IMAP folders on your phone etc.)
— That is one way of making sure you’ve equalised with the same mail server folder.
Hi PaulNormanNZ and jef… thank you kindly for your input. It sounds like Open Mail may be the way to go while we wait-out any possible fix to 5.8.x, should any fix actually be forthcoming.
It may be relevant to this discussion that HostGator and Bluehost (along with dozens of other webhosts) are owned by the same company, until recently known as Endurance International Group, merged in August with the Network Solutions/Web.com companies and now known as Newfold Digital.
It’s my understanding that when hosting companies are purchased by this megacorporation, their customers are moved to the parent company’s servers, so potentially anyone whose mail is hosted by a Newfold Digital company may be facing the same mail server configuration and therefore the same issue. There is a list of Newfold companies here (the blog post is old, but he keeps the list updated):
I’m no advocate of these companies (in fact, I advise my clients to avoid them like the plague), but their customers combined represent an enormous number of users. Even if they are in the wrong (which would be consistent with their MANY other performance and support issues), the K9 Mail developer may wish to reconsider his position due to the very large number of users who may be impacted, and unaware of it. Don’t think of it as knuckling under, think of it as supporting users who have horrible hosts and need all the help they can get.
Hello All,
I can confirm this very weird anomaly.
I have done the following:
two accounts one on bleuhost, another on gmail.
When sent from bluehost account to gmail, the email appears in the sent folder EVEN on the bluehost server. However, it never makes to the gmail inbox.
However, with all other servers I use, including gmail, everything is normal.
Finally, using other clients for android, it works fine.
My conclusion is that whatever it is it should be worked out between k9mail and bluehost.
Not sure if you figured out a K9 work around for the localhost ip issue, but it’s not hard to fix.
I always ask people in pissing contests, do you want to be right or effective?
Generally you want to be both, however, being effective general out weighs being right when it comes to managing people or programs. You get a better results.
I get the reason for the change to protect one’s IP address. I don’t agree with the use of 127.0.0.1, also known as loopback address. And it is suspicious when you have a request, authenticated or not, coming in with a non-routable address.
See RFC 1122 INTERNET LAYER October 1989
3.2.1.3
(g) { 127, <any> }
Internal host loopback address. Addresses of this form
MUST NOT appear outside a host.
Easy fix. Decompile apk.
Locate & Open the file - SmtpTransport.smali in a text editor
Change 127.0.0.1 (located near line 364) to a private network IP address, such as 192.168.1.10
Save SmtpTransport.smali
Compile apk
Install on device - your done.
Be sure to disable automatic updates for K9 app.
Probably still beyond the skill and/or determination of myself and I suspect the vast majority of users, not to mention only a few will ever reach this post.
Developer, if you’re reading this, please make the fix, or put an option for it in the Send settings.
Once a mail client has delivered a message to the mail service provider (MSP)'s server and gotten the acknowledgement that it has been accepted the client (any client) has no knowledge of or ability to control what that server does with the message. Even if the server doesn’t /dev/null the message straight out, there’s no way for the client to know that the MSP won’t block it at some further point. I.e., there is nothing that a client can do to know or guarantee that the host actually subsequently attempts to deliver the message out. That information can only come from the host in the form of a return (bounce). If the MSP’s server knows at the start that it doesn’t intend to deliver the message it should reject, rather than accept, the message. That way the user would know right away. Regardless the approach, standard best practice is for the MSP to inform authenticated users if their mail isn’t being delivered.
I understand that Hostgator is mostly to blame here.
I also understand that technically, the email client app is not notified of the dropped email.
However, the developer has been informed of the issue, and a fix (allowing users to revert back to an alternate delivery method) should not be that hard to implement.
The developer could help a lot of people by modifying/improving their app to deal with the reality of the situation, rather than simply washing their hands of the matter.
Do/can you trust an MSP that trashes its (authenticated) user’s messages, without notification? Getting a message past Hostgator’s first filter is no guarantee that they won’t trash it at some later stage, still without notification. If they were my MSP I’d be looking for a provider that comes closer to following best current practices.
So my hosting is up for renewal…BlueHost…and I’m not going to spent money on hosting that doesn’t work with K-9 and more importantly the strict mail send rules.
I don’t need web hosting.
I don’t want Google.
I need two IMAP accounts between two domains and I’d like to have around a gig of mail space JIC.
Hello everyone. I am new on this forum. I hope that what I write is correct and acceptable.
I have this problem with my Bluehost MSP with 6.200 K9 version. I solved as suggested from @
dejab and @cketti.
I did following modifications in SmtpTransport.kt
private fun buildHostnameToReport(): String {
val localAddress = socket!!.localAddress
// We use local IP statically for privacy reasons, see https://github.com/k9mail/k-9/pull/3798
return if (localAddress is Inet6Address) {
"[IPv6:::1]"
} else {
"[192.168.1.199]"
}
}
and now I can send my emails.
Is it possible that this simple change could enter the official application?
I’m using Thunderbird and recently switched to Android. I heard that k-9 mail is open source and in some partnership with Thunderbird so I was eager to try it, but after a few frustrating hours it seems like k-9 doesn’t want me if I use HostGator. As a long time HostGator user I can attest they’re quality has gone down over the years, so I’m not defending them, but my emails seem to work fine with most other email apps. Guess I’ll be going with Google for now. That was a really bad firt impression k-9, yet somehow I’m still rooting for you. So I figured I’d post.
