Bug 644161 - BCC - Privacy Problem When Forwarding Previously Sent Messages
Summary: BCC - Privacy Problem When Forwarding Previously Sent Messages
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-19 03:45 UTC by David Le Sage
Modified: 2010-10-19 06:38 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-10-19 06:38:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 567265 0 None None None Never

Description David Le Sage 2010-10-19 03:45:56 UTC
Description of problem:
If the user chooses to forward an email that he or she had previously sent to a list of BCC recipients, that list of recipients is displayed by default.

Version-Release number of selected component (if applicable):
Evolution 2.32.0-2.fc14 64 bit

How reproducible:
Every time.

Steps to Reproduce:
1. Create an email and send it to a BCC recipient.
2. Go to "Sent" box.  Select the same email that you just sent and click on "Forward." 
 
Actual results:
The "header" information from the previously sent message in the body text of the new message will include the BCC field and the name of the recipient.
  

Expected results:
BCC field and list of recipients should be omitted from body of forwarded email.

Additional info:
I do not if there is an option for this. When researching the bug, I tried Edit->Preferences->Mail Preferences->Headers.  "Unticking" BCC there made no difference.  

I would suggest that, if there is an option, displaying the BCC field in forwarded messages should be turned off by default to protect privacy.

Comment 1 Milan Crha 2010-10-19 06:38:36 UTC
Thanks for a bug report. I found an upstream bug [1] discussing the same, thus I'm moving it there. Please see [1] for any further updates.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=567265


Note You need to log in before you can comment on or make changes to this bug.