Kalle Kivimaa <killer@debian.org> writes: > Ben Pfaff <blp@cs.stanford.edu> writes: >> With Gnus+Mailcrypt, I was unable to vote with a signed but not >> encrypted ballot. The voting daemon claimed that there was some >> kind of quoted-printable problem. This surprised me: Gnus and >> Mailcrypt have not caused problems for me with any previous >> votes. However, this is the only ballot I recall containing >> non-ASCII characters, which could be the cause. > > As I used to have all my outgoing emails default to ISO 8859-1 charset > I was unable to vote with Gnus+Mailcrypt until I changed the default > to be ASCII. So, as I now had that same problem again, I'm guessing > the problem is with Raphaël's non-ASCII e+umlaut, which makes Gnus use > quoted-printable, which then isn't valid as seen by devotee (I'm > guessing that Gnus encodes the signed mail and devotee wants to > verify before decoding). Mailcrypt doesn't, as far as I know, support PGP/MIME (RFC 3156). PGP/MIME is the only standards-conforming way to do OpenPGP signatures containing non-ASCII text. Check your e-mail if it contains a top-level Content-Type of multipart/signed. If it doesn't, you used the vanilla inline OpenPGP type. Btw, an old rant on this topic: http://josefsson.org/inline-openpgp-considered-harmful.html In recent Gnus versions, PGP/MIME is supported natively. /Simon
Attachment:
pgp6UGSW3Qq32.pgp
Description: PGP signature