I recently sent an encrypted email via Enigmail to a friend who does all his crypto from the command line using gpg directly. He remarked that:
> I got your message. However, it was sent as an encrypted > attachment in a blank MIME message. The message was not > marked with the property "encrypted." I did a View Message Source on the message and saw a lot of headers and such which suggest that Enigmail is not simply encrypting the message, the way I would do manually with a command such as: gpg -o - -e -r [email protected] -r [email protected] -a In the message I saw elaborate headers such as: From: [email protected] Subject: test Openpgp: preference=signencrypt Autocrypt: [email protected]; prefer-encrypt=mutual; keydata= xsFNBFVTu9wBEAD3HrqNmAU5TPesso2t7QG+bq/Y9Brz0X... And this: Content-Type: multipart/encrypted; protocol="application/pgp-encrypted"; And then FINALLY this: -----BEGIN PGP MESSAGE----- hQIMA6Lhji0Goz+pAQ//RxnH969Jij+H9eupX698NC//p1PWVxDD2L9l0nruAKwz ... -----END PGP MESSAGE----- I was hoping there was a way for Enigmail just to compose a plain message with nothing but the "PGP" block, and no "Openpgp" or "Autocrypt" anything at the top. I actually tried disabling Enigmail "for this identity" entirely, and just doing the message manually, but that only worked for my default identity. If I chose a different identity, Enigmail inserted those Autocrypt headers even when I was sending a plain text email! -- Patrick _______________________________________________ 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
