l

#6526 is merged. Now I think we need further refactorings to async-imap to get rid of future cancellations there and stop token. Currently async-imap uses timeout internally and this means...

@WofWca Is this the first account (account ID, the one at the top of your account list) that got stuck? The last entry for account 1 and INBOX is this?...

> I didn't get the second question. Are there any more log entries for the "INBOX" of account 1 below? Or did IMAP loop for INBOX folder got stuck completely...

@adbenitez collected a log with https://github.com/ArcaneChat/core 1.159.5 where inbox loop got stuck on Android after logging `src/imap.rs:555: No new emails in folder "INBOX"`. Apparently this got stuck outside of the...

I have looked at `async-imap` again. It only implements its own buffering logic for reading and it does not look like it can get stuck in a loop to me....

> 4. Test async-compression over a stream that randomly stalls, splits or concatenates packets. Either improve turmoil for this or find some other way to simulate this. I tried to...

https://github.com/chatmail/core/pull/6848 was merged into core 1.159.4. But with 1.159.5 @hpk42 still got the problem of IMAP loop getting stuck. The log of an app running with 1 account looks like...

Core 1.160.0 includes change https://github.com/chatmail/core/pull/6910 that simplifies IMAP loop shutdown.

> There are no IMAP messages in the log, so IMAP loop got stuck long ago and it's unclear where exactly. The problem with recent Android is that it uses...

So we now have two logs. First log from a mailcow account, with INBOX loop and movebox loop (account IDs other than 4 are filtered out): ``` 07-15 13:39:32.051 4447...