GNOME Bugzilla – Bug 769254
Multiple Cc in separate headers don't show up in Reply All
Last modified: 2021-07-05 13:25:18 UTC
This is probably a bug in gmime, but this seemed like the most logical place to start with the bug report since I have not done a full code analysis. If an incoming email has multiple Cc headers, doing a "Reply All" to that email results in only the last Cc header being used, effectively ignoring the previous headers. It appears that the code in geary (or gmime?) assumes that there can only be one Cc header. Skimming over RFC2822, I could not find anything that particularly asserts that but I did find some references on the internet that talked about not adding multiple Cc headers. That said, mutt seems to handle multiple Cc headers just fine, so it would be nice if geary/gmime did that too. The email (with sensitive information removed) below is what triggered the bug for me. With this email open, click "Reply All" and watch only retracted3@domain.tld show up in the Cc. Return-Path: retracted@domain.tld X-Original-To: retracted@domain.tld Delivered-To: retracted@domain.tld Received: from retracteddomain.com retracteddomain.com [1.0.0.1) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by retracteddomain.com (Postfix) with ESMTPS id 7EF75483DBF09 for <retracted@domain.tld MIME-Version: 1.0 To: retracted1@domain.tld Cc: retracted2@domain.tld Cc: retracted3@domain.tld Subject: Retracted subject line Message-ID: retracted@domain.tld X-Priority: 1 From: retracted@domain.tld Date: Wed, 27 Jul 2016 10:18:23 +0530 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable
Hi Siddhesh, thanks for the bug report. Do both of the CC addresses show up in the CC field when Geary displays the message? Also, which version of Geary are you using?
Sorry, I somehow missed the notification for this question. I am using geary-0.11.1-2.fc24.x86_64. Both of the CC addresses show up in the CC field on display, it is just during a Reply-all that only the last one shows up.
No probs, I'll see if I can get a fix for this into 0.11.2.
Bumping outstanding feature bugs to the next stable release.
Actually, I don't think it's a GMime problem, it actually may be a problem with your mail server. When viewing a message, Geary uses the RFC822 message, which gets the headers from the actual message via GMime (which I think is doing the right thing here). However replying to a mail, Geary uses the "abstract" Geary.Email class, which retrieves headers from the database, which is populated from the IMAP ENVELOPE response when fetching the email in the first place. If you still have this or a similar message around, can you please verify this by looking up the email in the MessageTable of the SQLite database for the account: ~/.local/share/geary/[account name]/geary.db. The "cc" column for the message will likely only contain values from the last CC header.
(In reply to Michael Gratton from comment #5) > If you still have this or a similar message around, can you please verify > this by looking up the email in the MessageTable of the SQLite database for > the account: ~/.local/share/geary/[account name]/geary.db. The "cc" column > for the message will likely only contain values from the last CC header. I happened to have this around (I had to move to thunderbird but I fortunately did not purge the geary install) and I verified that the MessageTable has only the last CC header.
Hi Siddhesh, thanks for looking into that, it's very useful to know. Can I ask what made you switch to TBird? Was it a bug or missing feature in Geary?
It was this bug actually. In one of my email workflows I cannot afford (quite literally!) to miss even a single CC in the reply-all and I found myself doing that despite being aware of the problem - I can be pretty absent-minded. Such things usually encourage me to write and submit a patch (geary is quite nice otherwise, pretty close to what I would like from an email client), but I haven't had the bandwidth or the understanding to contribute effectively beyond submitting this bug report and giving you the information you need.
Fair enough. Fixing this will require a bit of infrastructure work (i.e. Bug 776251), but hopefully we can get that fixed in 0.13 and you can try Geary out again. :)
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.