[Camel] Threading view depends on message order
UID MOVE/COPY can change order of received messages (like for example Google does):
A00165 UID MOVE 67505,67521:67522 INBOX/something
A00165 OK [COPYUID 38 67505,67521:67522 1411,1410,1409] (Success)
the threading view relies on the order at least for messages with no real parent, like those from gitlab, which all have:
In-Reply-To: <issue_57366@gitlab.gnome.org>
References: <issue_57366@gitlab.gnome.org>
which can construct thread like this:
To explain, the last column is UID, where the lowest is the parent, but according to the date, the UID 25086 has been sent as the last, the overall parent should be 25088 instead.
This won't be a problem with comment-by-comment In-Reply-To and References header (gitlab constructs a flat tree, all messages are on the same level according to the threading headers).
Another example can be a move to a real Junk/Trash folder and then back, that also changes UIDs.