After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 791685 - Duplicates messages when sent to multiple mailing lists
Duplicates messages when sent to multiple mailing lists
Status: RESOLVED DUPLICATE of bug 750695
Product: geary
Classification: Other
Component: conversations
0.12.x
Other Linux
: Normal normal
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-12-16 16:34 UTC by Michael Catanzaro
Modified: 2017-12-18 07:10 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Catanzaro 2017-12-16 16:34:48 UTC
I'm getting a bit annoyed by Geary's handling of mailing list messages. If a message is sent to multiple lists that I am subscribed to, Geary displays the message twice: once for each list.

Gmail filters these out, so I never noticed this problem before, but I recently stopped using Gmail.

A quick heuristic would be to check the message body, ignoring the headers, and hide any mails that appear sequentially in the conversation if their bodies are identical. (The headers will not be identical, because the messages will be sent from two different mailing lists.)
Comment 1 Michael Catanzaro 2017-12-16 17:01:50 UTC
(In reply to Michael Catanzaro from comment #0)
> A quick heuristic would be to check the message body, ignoring the headers,
> and hide any mails that appear sequentially in the conversation if their
> bodies are identical.

That doesn't work, because list footers exist. :/
Comment 2 Michael Gratton 2017-12-18 07:10:04 UTC
Yeah, I haven't really looked into it, but I think the only way to handle this properly is to use the Message-Id header (if present), then probably fall back to the current method (received and size in bytes). This means we'll need to fetch a bit more data when retrieving new messages, but I think it will be worth it.

I've just broadened the scope of Bug 750695 since it's the same underlying problem, so marking this as a duplicate of that.

*** This bug has been marked as a duplicate of bug 750695 ***