GNOME Bugzilla – Bug 502913
Always carbon-copy (cc) option does not work anymore
Last modified: 2009-04-15 18:01:28 UTC
In evolution 2.21.3 on Mandriva Cooker, the options 'Always carbon-copy (cc)' and 'Always blind carbon-copy (bcc)' don't work anymore. I have the boxes checked and entered a email address, but new messages don't have the Cc: or Bcc: fields filled out.
This bug have also been reported during the ubuntu hardy development phase (evolution 2.21.92) : https://bugs.edge.launchpad.net/evolution/+bug/198167
There are some peculiarities to the behavior. 1) it only seems to occur for the first account, when the first account is the default account 2) when composing the new mail, if you select another account, then re-select the default account, the fields will be populated properly
I'll copy my original report from LP here for upstream convenience: I set Evolution to bcc myself on all messages. Under past releases of Evo, there was a bug #92036 that was active when emails were created via firefox links that caused the BCC default not to be used. This bug seems to have expanded to new messages created from within Evolution. Steps to reproduce: 1) Launch evolution 2) edit the default account and set (in the account editor) a value for BCC the "always blind carbon copy to" and tick the checkbox. 3) close out of the account editor and preferences window. 4) create a new email (File/New/Mail Message) 5) note that the BCC field is empty. I've noticed that this doesn't happen for all my accounts, just my default, main account. It only seems to occur for the first account in the list of accounts when that account is the default account. Hopefully that will help with reproduction. Versions: Evolution 2.21.92 evolution: Installed: 2.21.92-0ubuntu1 Candidate: 2.21.92-0ubuntu1 Version table: *** 2.21.92-0ubuntu1 0 500 http://us.archive.ubuntu.com hardy/main Packages 100 /var/lib/dpkg/status
*** Bug 510283 has been marked as a duplicate of this bug. ***
Bumping version to a stable release.
It was reported several times, so I think we can say it is a confirmed bug.
This seems to be working correctly in the new composer that will debut in Evolution 2.23.1. Hoping we can fix the old code in a 2.22.x update.
*** Bug 527538 has been marked as a duplicate of this bug. ***
Created attachment 109288 [details] [review] evo-account-defaults-settings This should fix the bug. But which commit actually broke this i'm not too sure. Will provide updates if i happen to notice it.
to #9: I have tried your patch, it does not work. The Bcc: field is still empty when replying to a mail. But when you create a new mail, Bcc: is filled correctly.
Oops didn't notice that scenario as "Replying to a mail" wasn't mentioned in any of the comments. Will update with a new patch in here. Thanks for trying the patch.
Setting the status accordingly.
*** Bug 530170 has been marked as a duplicate of this bug. ***
Created attachment 110079 [details] [review] Updated fix This should fix all issues. Matthew, this would not occur in the new composer as you have switched to EComposerHeaderTable :)
Looks correct, please commit to stable. Thanks!
Committed to Stable branch gnome-2-22 as r35434 http://svn.gnome.org/viewvc/evolution?view=revision&revision=35434
*** Bug 531145 has been marked as a duplicate of this bug. ***
*** Bug 531635 has been marked as a duplicate of this bug. ***
*** Bug 533316 has been marked as a duplicate of this bug. ***
*** Bug 526731 has been marked as a duplicate of this bug. ***
*** Bug 534434 has been marked as a duplicate of this bug. ***
*** Bug 538934 has been marked as a duplicate of this bug. ***
It seems as if the fix in 2.22.3.1 deals with BCC, but not with CC when pressing "reply to". Could someone confirm that? Even though the composer has been remade, several distributions have stable releases with 2.22.3.1, and I would appreciate if someone could suggest a fix. This bug is also reported at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479533
This should *not* be marked as resolved, since the "CC" is still not working on reply, and that is the subject of this bug report. ( I cannot seem to find any upstream patches that fix this! If there is - a link to this bug would be appreciated! ) The patch in r35434 fixes for "BCC" only. Patching for reply is easy, but doesn't work for "reply to all" (ie. it over-writes the "CC" list.) --- em-composer-utils.c.r35434 2009-04-06 18:09:35.000000000 -0400 +++ em-composer-utils.c 2009-04-06 15:54:32.000000000 -0400 @@ -1440,7 +1440,7 @@ e_msg_composer_hdrs_set_from_account (hdrs, account?account->name:NULL); e_msg_composer_hdrs_set_to (hdrs, tov); - e_msg_composer_hdrs_set_cc (hdrs, ccv); + /* e_msg_composer_hdrs_set_cc (hdrs, ccv); */ e_msg_composer_hdrs_set_subject (hdrs, subject); g_free (subject); Any patch suggestions?
(In reply to comment #24) > This should *not* be marked as resolved, since the "CC" is still not working > on reply, and that is the subject of this bug report. It's fixed in later releases, and we're no longer supporting 2.22.
It appears that this bug still exists in 2.24.5 and 2.26.1. The "Always blind carbon-copy" option _does_ work correctly, but the "Always carbon-copy" option only works on new messages, and does not work correctly when replying to a message. This appears to be due to the call to e_composer_header_table_set_destinations_cc in the reply_get_composer function. The composer has already filled in the values from the two "Always..." options in update_auto_recipients, but the CC line gets overwritten and the BCC line does not. It looks like the reply code needs to merge the CC destinations in, rather than just resetting them.