-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi, thanks for your reply. > Best choice is to use PGP/MIME - it doesn't have this problem. It's > always better to avoid problems than to find and optimize > workarounds. The same argument is true for the handling of attachments but there the option to remember the chosen way is implemented... > Which of your mail contacts cannot use PGP/MIME? Can you convince > them to use newer software which is PGP/MIME capable? I know that at least two of my contacts copy the inline text (especially if it is an encrypted e-mail) just out their webmailer, past it in a file and use gnupg via command line to decrypt it. And I personally actually like the "BEGIN PGP SIGNED MESSAGE" at the top of a message. People who don't know about encryption (which I think is sadly the majority) often ask me what this is about and then I can tell them. Of course, if I would switch to PGP/MIME they could wounder about the signature attachment and I could mention pgp in my e-mail signature but this is noticed and read by way less people then a line of all capital letters at the beginning of every e-mail. For the time being I'll stay with PGP/Inline and hope that no server on the way rewraps long line (if I don't have an error in my reasoning, this would break long links independently weather the mail is signed or not. So also people without pgp would complain, therefore I hope that this rewrap by a server is a rare case. Kind regards, Hauke -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAldbOQUACgkQjz8jfoq989eS+ACfTd0/zG8dUSxpAVeK865+VJXq oHkAn1wbgaJ5PTjozYplaPF7J2kB754R =Vie1 -----END PGP SIGNATURE----- _______________________________________________ enigmail-users mailing list [email protected] To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
