Hello Stephen,
Stephen Isard wrote in
<[email protected]>:
|Two questions:
|
|1. I have a pipe-text/plain filter that searches the text of messages.
|The filter doesn't do what I want it to on base64 encoded messages, and
|I think it is because the messages are sent through the filter before
|being decoded. Is there a way to make the filter apply to the decoded
|form of the message?
You mean something like
? set pipe-text/plain='?* cat -vet'
This should only see decoded data.
$ </dev/null s-nail -Rf -:/ -Spipe-text/plain='?*cat -vet' -Y'type 112'
~/sec.arena/mail/download
This outputs message 112, which happens to be a mailman base64
encoded message.
|2. The s-nail type command always gives me lines like
|[-- Message 1 -- 411 lines, 28593 bytes --]:
|and
|[-- #1.1 17/1062 text/plain, base64, utf-8 --]
|
|Of course those lines might sometimes be of interest, e.g., for
|debugging, but most of the time, I don't want to see them. They just
|take up space on the screen. Is there a way of suppressing them?
No. That not. We have a TODO entry
. `pipe' is total shit regarding MIME. We need some defined and
documented method to configure which parts are displayed and/or how
they are visually separated.
And then Martin Neitzel said over ten years ago something like
"PART.SUBPART should really be addressable directly". There
*must* be some entry in TODO which refers to that problem as such,
but it, of course, requires the MIME rewrite.
It of course is hard to drive in an automated fashion, since you
need to know the exact hierarchy of an email.
On the development branch there is an undocumented extension to
the `digmsg' command,
? digmsg x-create 116
? digmsg 116 x-part list
? digmsg rem 116
? digmsg x-create 116 -
? digmsg 116 x-part list
212
multipart/signed
multipart/mixed
text/plain
application/pgp-signature
? digmsg 116 x-part remove-at 4
210 4
? digmsg 116 x-part list
212
multipart/signed
multipart/mixed
text/plain
but *that* "x-dump" subcommand really does not decode for now
(same problem, but with hackery we could: it is not a regular user
visible thing; could even be made to dump just one part).
So no, the answer is we cannot. I have long (decade+) not used
alpine, but for example mutt shows these [info] messages, too.
(Ours were designed after them.)
I know original Heirloom does not have such noisy markers, but
markers there are (iirc).
Also since the entire message is dumped ...
So for now only something like this
$ </dev/null s-nail -Rf -:/ -Spipe-text/plain='?*cat -vet >&2' -Ytype112
~/sec.arena/mail/download >/dev/null
But of course that dumps all the text parts.
That merde should do for v14.9.25.
I have no idea *how exactly* i can improve *that* situation for
you? We need a MIME rewrite to be able to truly and officially
offer access to individually text parts.
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
|
|And in Fall, feel "The Dropbear Bard"s ball(s).
|
|The banded bear
|without a care,
|Banged on himself for e'er and e'er
|
|Farewell, dear collar bear
