[Enigmail] Disable PGP/MIME option

[Patrick Brunschwig]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Brian wrote:
> 
> Patrick Brunschwig wrote:
>> That's not supported. There are situations when it's technically not
>> possible to use inline PGP (e.g. if you attach a file via drag & drop
>> from another email, or if you attach a web page via File > Attach > Web
>> page).
> 
> 
> How do you deal with execs who will never understand the technical 
> subtleties?
> 
> How do you deal with these issues when you send to Outlook users?
> 
> If you primary customers can not read PGP/MIME emails you look like a 
> fool when you send them.
> 
> Execs DO NOT CARE that it is a standard or that they clicked the wrong 
> radio button.  If your execs' clients can not read your execs' emails 
> your ass is going to get chewed on.
> 
> In my opinion it is VERY short sighted of the Enigmail developers to not 
>   give an option to totally disable PGP/MIME sending.

As I have written, it's a technical limitation, and not a design
decision that I took actively. I can't overcome that limitation without
several months of work. Feel free to contribute if you want to, I just
don't think it's worth the effort given the benefit.

It's not my fault that Outlook still doesn't allow to properly support
PGP/MIME -- it's 7 years since RFC 3156 has been released and 12 years
since it's predecessor (RFC 2015) was published.

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

iQEVAwUBSAb9YXcOpHodsOiwAQILoAgAvp24Xh6tBJLcVOcFdglIOwtW5VSWWw5N
+bGSanhYi4qts/pY4XX0tGemFLQ47dKPgHekULRrXE5UUvTLcS+FnzF4A2dwqvE7
6SXvFTFmuiA3+rSr38fVQeYq4kUsfkPU66m4u9g1UUR4XqBPz5BMjpST7HwTcWTU
H5Eg/cdNIM/8JnJlIaAkU1PdG5mHVQRKhh9P7hl48G3yGvC6ydVq0KXuLag42ojf
7Kg5sBMNawJBCKVY7BUP7MBa7zRIrFuZ3qs2t3RV/b4bJikgs3aEt09/kLcLCNKc
bFzDMZKE3eNfZ4csU8Dn7Jfmimfld/PeeVhEF2dW/KBjcw4T+jDIpA==
=ZKxn
-----END PGP SIGNATURE-----