Hello Marc, We feel concerned about this issue and allocated @linagora resources to be doing some QA on this.
So far we did not encoutered issues (we tested K-9 Mail and BlueMail on Android 8.1.0) using James 3.3.x (cassandra-guice packaging). Could you: - Share exact apps versions - James version + packaging Also, did you enable QRESYNC + CONDSTORE ? At Linagora we disabled these options. As far as I understood from the exchange, these issues could had been caused by some mimeMessage format. Could you share such mime messages, if you identify them? Many thanks, Benoit On 02/07/2019 16:24, cryptearth wrote: > Hey Marc, > > I just checked on my Xperia z5 premium (android 7.1.1) with the stock > mail client. I've set up 3 or 4 accounts, one of them set to manual > sync, others to hourly, main to active idle. As I switched through the > accounts and folders I realized that my mail app also behave strange. I > quickly fired up wireshark on my local system and intercepted the wifi > from my phone through my network (yea, I have a bit of an unusual setup > that allows me to pull off such "stunts" - sometimes very helpful). > As far as I could check the IMAP traffic looks ok so far, but it seems > an issue either with the app itself or the mail lib it uses, as I also > get some de-sync issues. Just to test I "reset" the mail app, but same > issue still occurs. I seems that android somewhat not really uses the > stock javamail api lib but either some own homebrewn stuff or somethings > modified. Also it seems cache issues in the app it self as I can see > that some mails gets transfered over IMAP but don't show up or > "disappear" as you said. I guess that's an error with the app itself. > > I tested a quick demo with javamail 1.6.3 to see if the same issue occur > - well, it's a bit how-you-doin-it but as debug log shows when I'm > fetching the mails I first get the meta data and headers and then > can/have to fetch the mail part by part. > So if a mail consists of multiple maybe recursive mime-multiparts it's > possible the android app doesn't handle them correctly or the cache > get's messed up. > > So, unless you try to dive deep into the code for this app - and then > check what modifications maybe done by the device manufacturer (if any) > - you could try to file a bug report or try to search if such reports > already exists. I'm far from able to write some stuff for android, but I > guess re-implement it from scratch and doin caching right might would > solve the issue. Strange that other mail-apps also have issues - seems > like shared code that's causing it. > > Matt > > Am 02.07.2019 um 15:57 schrieb Marc Chamberlin: >> Hi Matt - >> >>> Btw: Are other clients consistent when you do changes like moving >>> mails around, marking mails as un/read, reply? Or are other clients >>> also show not-in-sync issues? >> Well the very fact that I am receiving and sending emails back and forth >> on the thread shows that James is working just fine from a Thunderbird >> application running on my Linux laptop! I am using STARTTLS and have >> used it with SSL/TLS connections so I know the keystore is working. And >> no problems with syncing and fetching emails. It is just the email >> client apps on my two Android devices that are giving me fits... And I >> am managing to send OK, just not fetch/receive. And both Android devices >> are acting the same way. >> >> I will keep poking around, take a look/search for caches etc... Thanks >> for the thoughts... Any one else got any ideas? >> >> Marc.. >> >> >> On 7/1/19 11:58 PM, cryptearth wrote: >>> Hey Marc, >>> >>> this looks strangs, at least I never seen such wired behaviour. I'm >>> currently running James 3.3.0 (final release commit) on my domain. I >>> also use Let's Encrypt wildcard certificate. As I guess you managed to >>> put a working keystore together (otherwise it would fail straight >>> away) we could asume that the error maybe could be in the message >>> handling of the used clients. >>> >>> As I'm a bit deeper into it using james for some mail-based stuff I >>> kinda implemented a small feature client to handle incoming mails. I >>> can only guess from my experience that a "normal" mail client would >>> have to implement some sort of local caching. If I would develop a >>> full featured mail client I would sync one time when the account is >>> set up and then chill in IMAP IDLE and respond to active listeners. It >>> could be that the client somehow throws out local cache for what ever >>> reason and fails to correctly re-sync. Btw: Are other clients >>> consistent when you do changes like moving mails around, marking mails >>> as un/read, reply? Or are other clients also show not-in-sync issues? >>> >>> It's also wired that different mail clients behave different. I don't >>> know about Android developement but only that most data stored between >>> uses of an app in a somewhat sleeping state saved when an app is >>> closed and reload when an app is (re-)launched. I could also be >>> something "stupid" as wrong file permissions (Android is somewhat >>> Linux after all - so it could struggle if some permissions messed up - >>> although they should kept in valid state by the app-managers). >>> >>> I'm sorry not to be able to help further as I can't see james as the >>> server or the connection between the app and james be the issue - >>> unless there something funny happens down at the connection layer. Is >>> it possible to factory reset any of the android devices to see if it's >>> set up "clean" keeps misbehave? If not: Try to clear caches and saved >>> data for the mail apps. Maybe it's some config issue. >>> >>> Matt >>> >>> Am 02.07.2019 um 08:46 schrieb Marc Chamberlin: >>>> Hi Matt - Thank you for taking the time to respond so quickly! >>>> Dunno if >>>> I will have time to play with other java applications but that is a >>>> thought. (I take off for Europe tomorrow so that may have to wait until >>>> I get back in Aug.) Do you know of a 3'rd party client email >>>> application >>>> that runs on Linux? I was just wanting to set up some email clients on >>>> my Android devices and ran into this snag. I have tried the >>>> connections >>>> using both TLS, SSL, and no encryption, all with the same no joy on my >>>> Android devices. The certificates are from LetsEncrypt and are >>>> fullchain >>>> certs. (They are in fact wildcard certificates for all the >>>> subdomains of >>>> my main URL) >>>> >>>> The log files for James don't show much, the only response I see, >>>> when I >>>> ask to fetch emails is these 3 lines - >>>> >>>> INFO 23:27:19,047 | >>>> org.apache.james.metrics.logger.DefaultMetricFactory | Time spent in >>>> IMAP-NOOP: 0 ms. >>>> INFO 23:27:19,065 | >>>> org.apache.james.metrics.logger.DefaultMetricFactory | Time spent in >>>> IMAP-EXAMINE: 16 ms. >>>> INFO 23:27:19,097 | >>>> org.apache.james.metrics.logger.DefaultMetricFactory | Time spent in >>>> IMAP-SEARCH: 25 ms. >>>> >>>> To my untrained eyes that almost looks like some sort of protocol or >>>> connection error is occurring since I would expect to see a lot more >>>> instrumented messages showing up in the logs whenever I click in the >>>> client to ask for a new download of messages. >>>> >>>> Marc... >>>> >>>> >>>> On 7/1/19 10:26 PM, cryptearth wrote: >>>>> Hey Marc, >>>>> >>>>> as most Android apps handling mail use javamail (at least I would, but >>>>> I don't know for sure if the android-api itself may offer some >>>>> "system-level" stuff wich is messed up) you can do so with a normal >>>>> java application run on your other clients. As more than one device >>>>> shows an issue one can say it mostly isn't something wrong with a >>>>> device, and you also tested different apps, so one can say it's not an >>>>> app causing it - but it worries that only the Android devices show >>>>> issues. >>>>> >>>>> Are you using TLS in any way on the server/s? If so: How did you set >>>>> the certificate up? Did you include the intermediate certificates in >>>>> the keystore? Otherwise, if you not use TLS, are you use a VPN? >>>>> >>>>> There many reasons this could fail. A quick test would be using >>>>> javamail and write some lines to test if it's an issue with javamail. >>>>> Also: does james log show any errors? >>>>> >>>>> Matt >>>>> >>>>> Am 02.07.2019 um 07:13 schrieb Marc Chamberlin: >>>>>> Hi - I started poking at this issue a few months ago and didn't >>>>>> find a >>>>>> solution so I thought I might ask again before I spend too much >>>>>> further >>>>>> time trying to resolve this issue. I am running James 3.4 (a snapshot >>>>>> version given to me to solve another problem) for my own SOHO nets >>>>>> and a >>>>>> few friends. Nothing big and for the most part it works fine when >>>>>> using >>>>>> it with email clients such as Thunderbird on Linux or Windows >>>>>> platforms. >>>>>> But I have a couple Android devices, a phone and a tablet and I have >>>>>> tried setting up a few different email clients on them all with no >>>>>> joy! >>>>>> They all seem capable of sending emails out through the smtp >>>>>> service of >>>>>> James, but I will be darned if I can get them to behave with imap. I >>>>>> have tried K-9, BlueMail, GMail, and the Samsung E-Mail clients. I >>>>>> have >>>>>> made the imap server connections pretty much identical to the >>>>>> settings I >>>>>> use in Thunderbird and Apple Mail and don't believe for a second >>>>>> that I >>>>>> am setting the Android apps up any different. So is there anything >>>>>> weird >>>>>> about Android that I should be aware of? BlueMail just shows me a >>>>>> spinning circle when I tell it to download my email from my server, >>>>>> K-9 >>>>>> does on rare occasion show me some emails but the moment I read one >>>>>> the >>>>>> rest just disappear and I can't get it to load any more or re-display >>>>>> the ones that it did manage to download for a short time. I also know >>>>>> something is partially working because all the folders and >>>>>> sub-folders I >>>>>> have defined in my mail accounts do show up. So I am puzzled, and >>>>>> asking >>>>>> because it seems James is the common denominator, any ideas? >>>>>> >>>>>> Thanks in advance... Marc... >>>>>> >>>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >>>>> For additional commands, e-mail: server-user-h...@james.apache.org >>>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >>> For additional commands, e-mail: server-user-h...@james.apache.org >>> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org > For additional commands, e-mail: server-user-h...@james.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
