Description of problem: Evolution doesn't automatically fill up the bcc / cc fields when it's configured to do so. Version-Release number of selected component (if applicable): I'm not sure what this means.. however, my Evolution has version 2.22.1 How reproducible: Every time Steps to Reproduce: 1. Open Evolution -> Edit -> Preferences -> Select email account -> Edit -> Go to Default tab -> Check "Always blind carbon-copy (bcc)to: " -> Added my email address in the field -> OK -> Close 2. Now open a new email. The bcc field is not automatically filled. Actual results: The field is not filled with the required data. Expected results: It should be filled with the email address set in the preferences dialog. (in my case my email address) Additional info: This functionality was working in FC8 and now it's not.
I believe this has been fixed in version 2.22.2. Can you please retest?
For the moment my FC9 installation didn't ask me to update Evolution.. I'll retest once the update becomes available from Fedora repositories... Thank you !
It's available now in the Testing repo. Should be available in the stable Updates repo in a week or so.
The BCC works for all 'new mail', 'reply' and 'forward', but CC works only for 'new mail' and 'forward', the 'reply' has the CC empty. (Not the exact version from F9, but the Rawhide one).
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as INSUFFICIENT_DATA.