On Thu, 16 Aug 2018 16:06:20 -0500, n...@trodman.com said:
> Should mhfixmsg run on each incoming message, or at least
> each one with mime headers? Maybe by adding to ~/.procmailrc?
>
What I do (after dealing with robo-mail from servers I know won't generate
anything needing fixing)
# Set
Hi Tom,
> Should mhfixmsg run on each incoming message, or at least each one
> with mime headers? Maybe by adding to ~/.procmailrc?
I think David Levine, mhfixmsg's author, runs it on every incoming email
in some way. See the two `Integration' in the man page.
--
Cheers, Ralph.
Hi Ralph:
On Thu 8/16/18 21:47 +0100 nmh-workers@nongnu.org wrote:
>> $ mhstore
>> storing message 1446 part 1.1 as file tmp/nmh/1446.1.1.txt
>> storing message 1446 part 2 as file
>> tmp/nmh/=?UTF-8?b?Y2xpbWF0ZSBmbHllciB1cGRhdGVkLnBkZg==?=
>> $
>>
>> Notice the filename for part
Hi Tom,
> $ mhstore
> storing message 1446 part 1.1 as file tmp/nmh/1446.1.1.txt
> storing message 1446 part 2 as file
> tmp/nmh/=?UTF-8?b?Y2xpbWF0ZSBmbHllciB1cGRhdGVkLnBkZg==?=
> $
>
> Notice the filename for part 2 is munged.
Search for `2047' in mhfixmsg(1).
--
Cheers,
Hi Ralph:
On Thu 8/16/18 19:20 +0100 Ralph Corderoy wrote:
>> What's the (config file?) fix so the string in
>> filename=SOME_UTF-8_CODED_STRING
>> associated w/below attachment headers
>> is properly decoded?
>...
>> Content-Disposition: attachment;
>>
Hi Tom,
> What's the (config file?) fix so the string in
> filename=SOME_UTF-8_CODED_STRING
> associated w/below attachment headers
> is properly decoded?
...
> Content-Disposition: attachment;
> filename="=?UTF-8?b?Y2xpbWF0ZSBmbHllciB1cGRhdGVkLnBkZg==?="
$ scan -forma
What's the (config file?) fix so the string in
filename=SOME_UTF-8_CODED_STRING
associated w/below attachment headers
is properly decoded?
--
thanks!,
Tom
--
$ mhn -version
mhn -- nmh-1.7.1 built 2018-05-19 10:39:15 + on epjdn.zq3q.org
--snip from troublesome email:
