Re: [nmh-workers] The message Body Shows but the Subject doesn't Decode.
Leonardo Taccari writes: > Hello Martin, > > The format file used by show should be mhl.format (that should be > in `mhparam etcdir`/mhl.format) and by default it has a: > > | Subject:decode > > line. > > Can you please check if the mhl.format has a `Subject:decode' > line? > > > (A bit unrelated but I think that `-f' option passed to strace > should also trace child processes, but at least as part of `show', > `mhl' is not invoked) My thanks to all as a lot of interesting things have come to light. I have been using nmh for over 20 years so some parts of the setup need modernization. I checked the mhl.format I am using and the From: and Subject lines need the word decode right after the : but here is what else I discovered: Messages from this group, for example have a fairly simple format and use mhl.format when being read. The message which started this discussion, however, is a mime message and uses mhshow. The strace program, using the -f option was very useful here to more quickly determine where to concentrate at any given time. On the system I am using now, my ~/Mail/mhl.format and ~/Mail/mhl.headers files had a creation date of December, 2009. Both files have mostly the same information in them but mhl.format is for non-mime and mhl.headers is for mime messages. The old files did not support From:decode and Subject:decode but showed as From: and Subject:. This was the crux of the issue. The replacements for those files are from December of 2016 and were the latest version of nmh in the debian Linux distribution. Things are certainly working better now. Thanks for your help in getting me pointed in the right direction. Martin McCormick -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [nmh-workers] The message Body Shows but the Subject doesn't Decode.
Ralph Corderoy writes: > Hi Martin, > Search for `Subject' in mhl(1), that will show you an example, and you > then want to read about `decode' in that same man page. Thank you. That narrows the scope tremendously. Martin -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [nmh-workers] The message Body Shows but the Subject doesn't Decode.
Hello Martin, "Martin McCormick" writes: > 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==?= > > [...] The format file used by show should be mhl.format (that should be in `mhparam etcdir`/mhl.format) and by default it has a: | Subject:decode line. Can you please check if the mhl.format has a `Subject:decode' line? (A bit unrelated but I think that `-f' option passed to strace should also trace child processes, but at least as part of `show', `mhl' is not invoked) -- nmh-workers https://lists.nongnu.org/mailman/listinfo/nmh-workers
Re: [nmh-workers] The message Body Shows but the Subject doesn't Decode.
Hi Martin,
> 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.
Search for `Subject' in mhl(1), that will show you an example, and you
then want to read about `decode' in that same man page.
If you still have problems, come back to the list.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
--
nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers
[nmh-workers] The message Body Shows but the Subject doesn't Decode.
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"
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
