[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
mpack/munpack, text/* base64 decode?
From: |
Karl Berry |
Subject: |
mpack/munpack, text/* base64 decode? |
Date: |
Tue, 26 May 2020 11:48:30 -0600 |
Hi Sergey (and all) - does mailutils provide utilities along the lines
of mpack and munpack to create or read mime messages? I could not tell,
but I did not see it. I'm sure all the functionality (and much more) is
there in libmailutils, but could not find a way to access it from the
cmdline.
Since m(un)pack is apparently no longer maintained, having a maintained
successor would surely be welcomed by many people. The best? version I
found was https://github.com/league/mpack/. All the heuristics and
binhex and other ancient stuff doesn't matter (IMHO), just the basic
mime pack/explode functionality.
However, I probably shouldn't be asking the above; it just seemed like a
good idea. What I actually want is something that I think munpack does
not do: given a msg with text/* base64-encoded parts, undecode them to
stdout, leaving the msg otherwise unchanged. As I'm sure you are well
aware, plenty of mailers nowadays decide to useless base64-encode
everything, making the messages opaque to grep etc. Sigh.
Surprisingly, I could not find any scripts or recipes to do that
particular job. Seems procmail has no built-in understanding of mime
parts. If you have any ideas, please send them my way :). --thanks, karl
P.S. At https://www.gnu.org/software/mailutils/mailutils.html#documentation
"TeXinfo" should be "Texinfo".
P.P.S. stylistically, the font size is being reduced on that web page
for no reason I can discern. Compared to, e.g.,
https://www.gnu.org/software/autoconf or automake, which use the font
specified by the user (me). I could not easily see what css is making
that happen.
- mpack/munpack, text/* base64 decode?,
Karl Berry <=