[Enigmail] About Supprting BCCed Recipients

[Patrick Brunschwig]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Robert J. Hansen wrote:
> John Clizbe wrote:
>> https://www.mozdev.org/bugs/show_bug.cgi?id=20867
>> Summary:RFE: Pass BCC recip to gpg with --hidden-recipient instead of -r
> 
> Given this RFE has such a large potential impact on users and there is
> no consensus for if it should be implemented, I think this RFE needs to
> be tagged NOTNOW and work shifted to other things in the RFE queue.
> 
> I do not think this RFE is ripe for implementation.  Let's keep
> discussing it, sure -- but let's not implement it now.  Six months from
> now, maybe.

I tend to disagree here: currently, Enigmail doesn't allow to send
emails to BCC'ed users at all. Thus, any solution that allows to send
encrypted emails to BCC'ed users is an improvement; at least as long as
the users are informed about the consequences and can decide how to
proceed. Even if we only reach a (simple) 80% solution in a 1st step,
it's still better than disallowing BCC-emails completely. Thus I think
it's still worth doing it.

- -Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEVAwUBSgu5oncOpHodsOiwAQjLCwgAsv7LGRVmSLWt2el2gPLEvUyHa3mUQFiU
O9BSvfaNfbw8mXrpNwtxhsCKU0Od/MbM3VDqZtRAGHYH99pWbCddQ0svVMjCr46P
c41EpoMKJNZwtR40+s1xcMIiJsgOdjPoBHlHlhoPsp4rmuByiaOqLSR6xAFkeD2x
Nex6g4skHIoECO8mDI0Wv9LycEEfuNHVygNkrnyqhyFPLp5Zl3PcJ7gJ/nXm96fc
oxFgZv2iqlL/mDUw+FSrcukrZQYhz/dSmfeKisaDjtMtOhL1QIeQKjB0kEwWsi2X
NMAj5D0S5vfPYS3JEkka7lldM1R4jZRA68P3cnxE2lAiNv3e6q1KNw==
=INRZ
-----END PGP SIGNATURE-----