If I am understanding this issue correctly, a plausible real world scenario for bcc'ing encrypted recipients is one I ran into last week:
I am working on a project that requires interaction with 3 different stakeholder teams. All use encrypted email, but do not interact with one another directly, and that is by design. It was a simple enough task to copy/paste the original message into new messages for the other teams. But it would have been convenient to be able to BCC the whole group at one time. I use myself as the To recipient. My personal preference is to see the same encryption behavior everywhere - where there are recipients w/o a key combined w/recipients that do have a key, warn that the message will be unencrypted. A prompt before send may be better than a status icon imho. On 1/6/2015 11:24 AM, Phil Stracchino wrote: > On 01/06/15 11:23, Patrick Brunschwig wrote: >> If you think this should be changed, then you're invited to >> discuss this here. I never use BCC recipients in conjunction with >> encryption, so I can't really estimate how to proceed here. > > I tend to agree; I have a little difficulty imagining a plausible > real-world scenario in which you would want to send Alice an encrypted > message and bcc: Bob on it. > > > > _______________________________________________ > enigmail-users mailing list > [email protected] > To unsubscribe or make changes to your subscription click here: > https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net > _______________________________________________ enigmail-users mailing list [email protected] To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
