Just a thought

[John Clizbe]

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
-- 
John P. Clizbe                      Inet:John (a) Mozilla-Enigmail.org
You can't spell fiasco without SCO. hkp://keyserver.gingerbear.net  or
     mailto:pgp-public-keys at gingerbear.net?subject=HELP

Q:"Just how do the residents of Haiku, Hawai'i hold conversations?"
A:"An odd melody / island voices on the winds / surplus of vowels"

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 678 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20090426/15a88bbc/attachment-0001.pgp>