Re: IMAP <-> nmh syncing
Michael Richardson <[email protected]> Sun, 08 Mar 2026 21:16:56 -0400
| Newsgroups | gmane.mail.nmh.devel |
|---|---|
| Message-ID | <[email protected]> |
--=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ken Hornstein <[email protected]> wrote: > I hate to crap on people, but ... I was curious and I dug back through > things. As far as I can tell: Thanks for tracking that down. Please unicast me the original to me... uuencode/zip, whatever. > - 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 doub= le > checked this (see the email I mistakenly sent to the list). NMH + MH-E, yes. > - 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 Okay. > 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. Yes. I'll see if it happens twice. =2D- Michael Richardson <[email protected]> . o O ( IPv6 I=C3=B8T consulti= ng ) Sandelman Software Works Inc, Ottawa and Worldwide --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAmmuH4gACgkQgItw+93Q 3WXu0ggAjLfH0GNlTdbA5eA+t15y79VrQtr6DZV3fJ6xRXufgBrLuhvvHaRcwEOu xmSyt/6BvhsoaZvm6BczXtXmlJCDNFi7dbTsvYwjvc6NX7psaz+GQLDNf103gTpF EYqY0u6VllS1t6meDPTGCBD3WFgYibP7fv7s39oCmRMTuFHOSoD/favk++FoTS+h QuY+3Z+/OgMwH886akY9uraG34s7V4FByUzAPiIv0bnHa5R2qv5KJd8rGWsYqrOy fd2IYNr6VMfYzYUJmlOy+SG2I2DuvwZfUT1WV37zToBmBE1oO77X3uQmsFR1md1c e0F1THRBY27CJLIEIUMJgrBw2KZzrA== =9p9p -----END PGP SIGNATURE----- --=-=-=--