Just a thought

[Harakiri]

--- On Sun, 4/26/09, John Clizbe <John at Mozilla-Enigmail.org> wrote:

> From: John Clizbe <John at Mozilla-Enigmail.org>
> Subject: Re: Just a thought
> To: "David Shaw" <dshaw at jabberwocky.com>
> Cc: "GnuPG Users" <gnupg-users at gnupg.org>
> Date: Sunday, April 26, 2009, 6:04 PM
> David Shaw wrote:
> > On Apr 25, 2009, at 6:14 PM, John Clizbe wrote:
> >>
> >> Enigmail passes GnuPG a list of recipients to
> encrypt to. It does not
> >> generate separate messages, only the one.  This is
> a constraint of
> >> Thunderbird's architecture.
> >>
> >> BCCed recipients are treated as just another
> recipient. There is only
> >> one copy of the message and one set of encrypted
> session keys.
> > 
> > I'm not sure if Enigmail has sufficient control
> here (due to the  
> > Thunderbird restrictions), but if possible, it might
> be wise to handle  
> > Bcc's recipients with --hidden-recipient instead
> of --recipient (i.e.  
> > "-r").  That would better duplicate the
> standard expectations of a  
> > user using Bcc: the regular recipients can all see who
> the recipients  
> > are, but not the Bcc'd people.  As things stand
> now, any recipient can  
> > see who was Bcc'd, which sort of removes the
> "B" from the Bcc.
> 
> Excellent suggestion, David. Thank you.
> 
> Filed as an RFE in Bugzilla:
> https://www.mozdev.org/bugs/show_bug.cgi?id=20867

Bad idea, read my comment on the bug - what good is a setting when you can only communicate with people which use GPG - and the other 80% which use PGP Desktop cant decrypt your message?