[Enigmail] About Supprting BCCed Recipients

Daniel Kahn Gillmor dkg at fifthhorseman.net
Tue May 12 09:58:44 PDT 2009


On 05/12/2009 12:19 PM, Patrick Brunschwig wrote:
> I forgot that the forum needs registration. Those who don't want to
> register can send an email to the following address:
> poll at mozilla-enigmail.org
> 
> Please indicate your answer to the following question:
> 
> How many of your correspondents use a product (like PGP) that doesn't
> support hidden keys?
> 
> [ ] More than 50%
> [ ] Between 20% and 50%
> [ ] Less than 20%
> [ ] None (i.e. 0%)
> [ ] I don't know what software my correspondents use for encrypting messages

I believe that everyone who participates on public mailing lists like
this one *must* answer in the latter category, simply because we have no
idea who else is subscribed to the lists we use.  Of course, mails sent
to lists are not usually encrypted so perhaps this doesn't matter.

Perhaps it should be rephrased as "how many people do you send encrypted
mail to that cannot read it with hidden keys?"   Even so, it seems like
we might be asking the wrong people.

Also, please don't enable hidden recipients by setting --no-throw-ids,
which paints with far too wide a brush.  Better to use
--hidden-recipient for the specifically Bcc'ed folks.

Most simply, i could see this as the default behavior
(--hidden-recipient for Bcc), with the ability to set a per-recipient
rule disabling the feature.

	--dkg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 890 bytes
Desc: OpenPGP digital signature
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20090512/40a211e4/attachment.bin>


More information about the Enigmail mailing list