On 07/09/2018 22:31, Patrick Chkoreff wrote:
>> Can anybody think of something more I can do to force Enigmail NOT to
>> set up one of those "encrypted.asc" file attachment things,
> OK I think I figured something out. I went into the Per-Recipient rules
> and set PGP/MIME to "Never". I sent a message to my friend Bob and saw
> this:
>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=utf-8
> Content-Language: en-US
> Content-Transfer-Encoding: 8bit
What mail client is Bob using? The first message part header you
quoted[1] is correct for PGP/MIME which I would have thought any modern
mail client should be able to decode.
Footnote:-
1: If this is the message part header (which you quoted)
Content-Type: application/octet-stream; name="encrypted.asc"
Content-Description: OpenPGP encrypted message
Content-Disposition: inline; filename="encrypted.asc"
then this will be in the main message header:
Content-Type: multipart/encrypted;
protocol="application/pgp-encrypted";
boundary="<longstring>"
--
Mark Rousell
_______________________________________________
enigmail-users mailing list
enigmail-users@enigmail.net
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
