MIME or inline signature ?

[des-apare.cido_77 at autistici.org]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

> Maybe I cannot offer a big rule for THE preferred way. Jerry is
> right, but maybe we HAVE to deal with recipients who have no
> influence to take a mail client which is capable to handle PGP/MIME
> sigbatures properly. Then it is also MY problem.

I agree. With my PGP contacts I learned, that some can't handle
PGP/MIME mails. The experience is, that the Addon Mailvelope (Firefox,
Chrome) can't handle at all mails with attachment in PGP/MIME format.
Also the Client K9 for smartphones.
A compromise would be to set up per-recipient-rules in Enigmail to
send inline mails to these contacts.

Best regards

Anton
- -- 
des-apare.cido_77 at autistici dot org
2048R/0x6FE6F0B56FB0CD78, 2014-03-06
PGP: E87B D4A1 45A6 8D97 F672 E50E 6FE6 F0B5 6FB0 CD78



On 13/02/15 03:23, Matthias Mansfeld wrote:
> 
> Zitat von Xavier Maillard <xavier at maillard.im>:
> 
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
>> 
>> Hello,
>> 
>> in my quest of the perfect setup, I am asking myself what is the 
>> prefered way to sign a message: inline (like this one) or using a
>> MIME header ?
>> 
>> Is there a big thumb rule to respect ?
>> 
>> Regards - -- Sent with my mu4e
> 
> Maybe I cannot offer a big rule for THE preferred way. Jerry is
> right, but maybe we HAVE to deal with recipients who have no
> influence to take a mail client which is capable to handle PGP/MIME
> sigbatures properly. Then it is also MY problem. If your mail
> client is able to select the way it signs depending on the 
> recipient's address (for example GPGRelay, in fact a nice local
> proxy for mail clients which are completetly unable to do anything
> wich GnuPG) then you can let it sign for all "default" recipients
> with PGP/MIME and only for these who cannot handle this, with
> inline signature.
> 
> Regards Matthias
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQEcBAEBCAAGBQJU3ZPfAAoJEG/m8LVvsM14AM8IAJKwfqMc1k+1Y2YJ0tjbGC6F
jrFIuxaqiRkr0Q0rg6Ty1Po8zzfctxuXAMnrRapZAL+ldyvkNrGRW07U0Bkhg83M
C5k32cCHuyGjeT1v4Mcx4gExb33zoQBpHLi0EOZcW4VvNQ6RCpK8fBUIGgsi+tJM
WBDuuPc70qFWVoA0JJP8vcdGzDg/DXwNtX0aiCBuzXZk8nsZUZKMkWAGDCkzrhpq
RF819j1R7L+sUv6NSesoanWuutwDhdunjcEiGbklv0xQ4nlPBgwE6IkN862stuI3
Za8VziG+BdEwvBi0Zi5mlUMkOl1VhQ+x7BPvMTurUm35csoZNngEIMfdwhDQzHU=
=EfOk
-----END PGP SIGNATURE-----