Notifications from todo.sr.ht look like:
[-- The following data is PGP/MIME signed and encrypted --]
Ticket resolved: fixed
*?????? referenced this ticket in commit [91b3272].*
[91b3272]:
https://git.sr.ht/~nabijaczleweli/urlview-ng/commit/91b3272 "Beep on
unknown KEY_CODEs instead of passing them as chars"
--
View on the web: https://todo.sr.ht/~nabijaczleweli/urlview-ng/5#event-261404
[-- End of PGP/MIME signed and encrypted data --]
Which is Not Great.
Attaching the problematic mail raw,
and the problematic mail how neomutt attached it with attach-message
(decoded and reassembled as-if it hadn't been encrypted).
The raw decrypted body is
-- >8 --
$ gpg -d < raw
gpg: encrypted with 4096-bit RSA key, ID ED46733532B811FB, created 2015-08-23
"наб <nabijaczleweli@nabijaczleweli.xyz>"
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain
Ticket resolved: fixed
*=D0=BD=D0=B0=D0=B1 referenced this ticket in commit [91b3272].*
[91b3272]:=20
https://git.sr.ht/~nabijaczleweli/urlview-ng/commit/91b3272 "Beep on=20
unknown KEY_CODEs instead of passing them as chars"
--=20
View on the web: https://todo.sr.ht/~nabijaczleweli/urlview-ng/5#event-2614=
04
gpg: Signature made Sun 01 Oct 2023 05:17:21 CEST
gpg: using RSA key 447B69E4B34BE90BC829A0E9659704D1A38A93AE
gpg: Good signature from "sr.ht dispatch (Address for automated emails from dispatch.sr.ht) <dispatch@sr.ht>" [unknown]
gpg: aka "sr.ht <admin@sr.ht>" [unknown]
gpg: aka "sr.ht outgoing (General purpose outgoing sr.ht address) <outgoing@sr.ht>" [unknown]
gpg: aka "sr.ht todo (Address for automated emails from todo.sr.ht) <todo@sr.ht>" [unknown]
gpg: aka "sr.ht builds (Address for automated emails from builds.sr.ht) <builds@sr.ht>" [unknown]
gpg: aka "sr.ht git (Address for automated emails from git.sr.ht) <git@sr.ht>" [unknown]
gpg: aka "sr.ht meta (Address for automated emails from meta.sr.ht) <meta@sr.ht>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 447B 69E4 B34B E90B C829 A0E9 6597 04D1 A38A 93AE
-- >8 --
which sure as hell doesn't look like it's got "utf-8" in there anywhere?
(Note how the message Subject (not encrypted) isn't RFC2047-encoded either:
Subject: Re: ~nabijaczleweli/urlview-ng#5: Mousing around while editing URL inserts ƙ
(so if I were using outlook I'd be hosed but I'm not so who cares).
Still.
Oddly, in the bounce mail I got from the first time I sent this with
the attachments message/rfc822, the To: is fully-RFC2047-encoded.
So idk.)
Best,
наб