>Steffen Nurpmeso <[email protected]> wrote: > > Michael Richardson wrote in > > <[email protected]>: > > > To mention that somewhere is a bug, as there was that intermangled > > RFC 2047: > > > =?us-ascii?Q?=3D=3FUTF-8=3FQ=3FH=3DC3=3DA5kon=5FAlstadheim=5Fvia=5Fnmh?= > >Not sure it was me. >I think it got to me like that.
I hate to crap on people, but ... I was curious and I dug back through things. As far as I can tell: - The original, correct RFC 2047 encoded email address made it to the mailing list and at least to my inbox. - The email header Mike sent out was correct (in that it was formatted properly), but it was actually the RFC 2047 encoding of the existing encoded RFC 2047 header. As far as I can tell, this is not something nmh will ever do as it scans the header and if it doesn't find any 8-bit characters it will simply return the original header and I double checked this (see the email I mistakenly sent to the list). - As far as I can tell, Mike, you were the originator of this encoding and it didn't appear anywhere else before that. I don't know if something changed the message before it got to your mailbox or what, but I'd say something on your end decided to encode an already-encoded header. It looks like you used MH-E to compose that message, based on: X-Mailer: MH-E 8.6+git; nmh 1.8+dev; Emacs 30.1 So I'd maybe start by looking at MH-E. --Ken
