GNOME Bugzilla – Bug 750695
Merge duplicate messages sent to self, or one or more mailing lists
Last modified: 2021-07-05 13:24:38 UTC
When emailing a mailman mailing list, Geary will display both the message from the sent folder as well as the same email thats distributed by the mailman bouncer, displaying two messages with identical contents in the thread.
Do these two messages have the same Message-Id?
Just checked and I can confirm they do
Filtering on that might be a reasonable approach, then.
This is also true if you email yourself directly. We have two choices here - filter out the sent message, or the received message. In either case the conversation needs to be otherwise treated as if both messages are present, for listing, sorting, labelling, etc. 1. If we filter out the sent message, then when the message is received, it will be marked as unread, will re-appear in the INBOX, can be managed from there. 2. If we filter out the received message, then a lot of special cases need to be taken into account: How to show the unread state of the received message, any mailing-list-related headers it may have, etc. So to my mind (1) is the way to go here. It might be worth introducing a notion of a logical message, that can be composed of one or more actual messages, to implement this. I'm kind of surprised Geary doesn't handle this already with its GMail label support however.
I thought I might add: This is also an issue if you're CC'd on a mailing list. It gets really out of hand if you send a message to a mailing list you're subscribed to with yourself CC'd (as git send-email does), as you end up with three copies of each message in the thread. Being CC'd in reply makes keeping track of what's happening in the thread especially challenging.
Retitling to make this a bit easier to find.
*** Bug 791685 has been marked as a duplicate of this bug. ***
(In reply to Robert Schroll from comment #1) > Do these two messages have the same Message-Id? In my case, the messages *do* have the same Message-Id. I didn't know about that. That's great!
This comment from Bug 713319 might be worth looking into: > Updated by Tiago Quelhas 11 months ago > > JWZ's algorithm [1] is worth taking a look for this, as it is the _de facto_ > message threading algorithm for MUAs. It threads primarily based on References > /In-Reply-To headers, but also includes a fallback heuristic based on subject > lines. Obviously, Geary doesn't really need to know the nesting order of > messages within a conversation, so the full algorithm isn't required; but we > could use the part concerned with identifying which messages belong to the > same conversation. > > [1] http://www.jwz.org/doc/threading.html
Another use case from Bug 733388: Being CC'ed on a mailing list message, and getting one copy from the list and one directly, or receiving the same message sent by to two different mailing lists.
*** Bug 791847 has been marked as a duplicate of this bug. ***
*** Bug 714568 has been marked as a duplicate of this bug. ***
Bump tickets to 0.14 that aren't going to make 0.13.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/geary/-/issues/ Thank you for your understanding and your help.