On 26.03.15 01:38, Daniele Nicolodi wrote: > On 25/03/15 23:56, Ville Määttä wrote: >> > On 26.03.15 00:14, Ingo Klöcker wrote: >>> >> So it's not mailman that's not smart enough, but the mail clients >>> >> the other recipients are using. Mail clients showing a >>> >> "signature.asc" attachment probably do not understand PGP/MIME >>> >> (which isn't that unusual because only a handful mail clients >>> >> support PGP/MIME out-of-the-box without additional plugins). >> > >> > It seems to me that emails sent and signed by Thunderbird + >> > Enigmail are displayed just fine by it. No signature.asc quirks. >> > But emails sent by others are displaying the attachment in addition >> > to the normal Enigmail added UI signature information. Ingo, Doug, >> > Samir and Bob; I see the attached file for each of you but not my >> > own PGP/MIME mails routed back to me from the list :). > The difference must be somewhere else: I use Thunderbird 31.5.0 and > Enigmail 1.8 (20150316-1815) and, while it recognizes the signatures, > I see the attachment "signature.asc" for all the PGP/MIME signed > emails I've checked.
I sent a signed message to Daniele off list. Signature recognized fine and no attachment. So a bug, i.e. the extra attachment, in Enigmail's reading of mails that have gone through Mailman even though Mailman produced MIME should be valid? -- Ville
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
