There is a message on a discussion group which I can read just
fine but the subject line is not decoding.
Subject:
=?UTF-8?B?UmU6IFtibGluZC1oYW1zXSBXaGlzdGxlciB0byBMYXVuY2ggTmV3IExTTSBDYXBhYmxlIFNjYW5uZXJzIOKAkyBXaGlzdGxlciBHcm91cA==?=
Recently, it scanned still encoded and also showed as shown
above as encoded but I fixed the scan by modifying a
formatting file created just for scanning messages called
scan.sub
%4(msg)_ \
%(decode{subject})
That's all it took. The original version of that file was
%4(msg)_ \
%{subject}
A scan of that message now shows as
19+ 06/11 "Jordan Gallacher Re: [blind-hams] Whistler to Launch New LSM Capa
When I show 19, for example, I still get
(Message blind-hams:19)
Date: Mon, 11 Jun 2018 14:12:48 -0500
From: "Jordan Gallacher" <jordanandseptem...@gmail.com>
Subject: =?UTF-8?B?UmU6IFtibGluZC1oYW1zXSBXaGlzdGxlciB0byBMYXVuY2ggTmV3IExTTSBD
***YXBhYmxlIFNjYW5uZXJzIOKAkyBXaGlzdGxlciBHcm91cA==?=
Here are some headers showing what type of message it is.
The rest of the body has no problem on a vt100-style screen.
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
One diagnostic I did do was to try to determine which
filter is being called by using strace.
strace -e trace=desc but mhl got called so I didn't see any way
to slip the
%(decode{subject})
directive in to give us decoded output rather than raw data.
As problems go, this is not a show-stopper but it is
certainly not as useful as Subject lines in plain text.
I discovered this by accident while writing a small perl
script to allow one to scan a large number of messages that have
been sorted with sortm -subject. The perl script prints the
first message of a new thread and then suppresses all other
messages so one can read a larger spew more easily. Subjects
that are printed as encoded garbage might sort but you don't know
what they are so it was nice to see the plain subjects. That's
when I noticed that show did show okay minus a clear-text
subject.
The LANG environment variable for this system is
LANG=en_US.UTF-8
so anytime we can turn gibberish in to something readable is good.
Thanks for any constructive help.
Martin McCormick
--
nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers
