iequidoo

> It's possible that I sent or received messages 2288 to 2312 on the mobile app (android), then opened the desktop app, sent 2251 and only then did the desktop...

In fact we already complicate sorting with the `\Seen` flag because we don't check it for a new message arrived, but we add it in a `InSeen` state and this...

These jobs: > Rust tests (macos-latest, 1.82.0) for some reason are in the `Expected — Waiting for status to be reported` state, in dependabot PRs too.

So, now the changes are limited to the `deltachat-ratelimit`. I only renamed `WebxdcInfo::send_update_interval` to `send_update_interval_ms` in addition because it's not related to JS land directly

A fix i can imagine here is to sort by INTERNALDATE not only messages from a particular folder, but from all folders, before passing them to `receive_imf_inner()`. The problem is...

Another possible fix is to leave this unordered processing of folders as is, but search `Message-ID` in the already known references, this way we can insert an unordered ("missed previously")...

> Edit: Oh wow, I have found the PR in regard to the chronological ordering: #5800 Unfortunately, this PR won't help in your scenario, it only sorts new received outgoing...

Btw, i just received several mails from github and that's how it looks curently:  These are unrelated threads, but even Gmail Android app merges them to a signle thread....

> Have you checked that during failed configuration device message is not added? During configuration `Imap::connect` is called here: > > https://github.com/deltachat/deltachat-core-rust/blob/f7a705c6da9e6805f12156581aa867740b382756/src/configure.rs#L423 > > It adds device message if it...

I tried to simplify the logic and now (re)configuration doesn't add device messages about wrong password