-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 29.03.15 18:44, Mike Acker wrote: [...] >> Fixed in v1.9. > I think we need to re-think this protocol question: if the user > selects either (a PGP Signature or PGP Encryption or both) and (the > message is in HTML format) then the user needs to use PGP/MIME and > that should be the automatic default. certainly OK to have a > switch to change the message to plain-text and shift to PGP/Inline > but at this point I think most eMail messages are written in HTML. > > as things stand I have to go back to the Enigmail dialog and > re-select PGP-MIME each time I want to use it. Not Good.
The protocol question has already been decided. Enigmail 1.9 will use PGP/MIME by default. Furthermore, you can change the default to PGP/MIME in the account settings, and you can specify PGP/MIME to be the protocol for certain specific email addresses using per-recipient rules. I doubt that more automatic changes would make things easier. - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVGC5uAAoJENsRh7ndX2k7LioQAJYYnsSlZEnTQtOP+zx7jPrw hcoAL3uZb2ap1X8HUU37ErLrJ+ehYhN6w4hah82Vsif+XcezyXogD/hvW6ntKZEe 6HDgUDdbBfaYci80QPjVqKV4vEAS4K3g7JxKxbgSbQ0enAhvurQ0eTsUW/l5CQBV +URZqRyJtqDNkl1Ob4hy2cugWmt3qMTDC6U9RyYtYEAouJgCUFDcy/Gyj2smQfxn HqFkLlOn6sqGEfHFxINK/ZuziQT+VpBQXm3A/Uzk6YqBFibUNp1kWZyEDgAKALgT 9U3NcjScKWx4eFQedv6Iefocaz99FZEVP20m+6QJW7vDGs9sjzNZyDwuunUEfT1n vxzJvefKJj0erHcx6pTXYbDtLheL/O0aPArSPx7wt3ySP3z0bqHU1mKgaGbGHoiu sMAe2tWudWHuAY9OwtEjsSzW5AoD28x2kTD8CFHsDxtL5u+Ba7JDu/9qA1JQU3dc bArCcELdUsvp05S/UOYSRyNvJ6UqxIardhSd1uHK2TBhY4Kvlqlcge9JvSDeMusI gqLHvD5jzPgjVvRgyHRfgt+U47Ncs+6VC4cB2gqSx7M5EC9U+7hcRaulPq59X8uC mpHo9LB5+DIIj5aPIniJC3dliBG6nhwHgCZbNJ+FTpuKrdUQb1AQl5uWlIvFkZml 8oc9qb91IUWaa6U2HEFs =MsS2 -----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
