valdis.kletnieks@vt.edu wrote:
On Thu, 14 Feb 2019 22:51:43 -0500, Ken Hornstein said:
There's something else wonky about Paul's note. My preliminary guess is
that something got mangled when MailMan tacked the us-ascii footer onto
Paul's utf-8. The end result is that exmh gets confoozled, even though
it usually gets this sort of thing right.
FWIW, I saw the same exact thing. I thought maybe it was because of the
invalid encoding, but maybe that isn't right
Found it.
Content-ID: <6521.1550182708.1@grass>
Removing it causes exmh to behave. Added to my bug list.
Did you happen to see the same behavior with Mark Bergman's message,
in this same thread? I ask because we both generated Content-ID headers
with no domain part (i.e., no dots after the '@').
paul
=----------------------
paul fox, pgf@foxharp.boston.ma.us (arlington, ma, where it's 42.3 degrees)
--
nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers