Re: MIME decoding via metamail

Jens Peter Secher <[email protected]> writes:

>         KEYHEADS='*' MAILCAPS=mailcap metamail -d 2>&1
>
> [...]
>
>         encodedinlined<type>

that was a worthwhile experiment!

> I am not sure about the message/* type (I just looked in my own
> /etc/mailcap file).  Does anyone with a better understanding of
> mailcap files have a better solution?  Why can't I write 
>
>         *; echo encodedinlined%t | tr -d -c '[:alpha:]'
>
> instead of repeating similar lines?

you might try:

       */*; echo encodedinlined%t | tr -d -c '[:alpha:]'

i have had message/rfc822 messages, they are nothing more than a
normal email complete with headers.  mime can tell from the boundary
line and the type what it is supposed to do with it.

have you also some of the resulting "encodedinlined.*" words in your
~/.idata statistics?  i bet this is worth trying and increasing ifiles
usefulness on machines with fast disks.  it will propably not work
with all that spam that deliberatly violate standards to get their
shit thru.  i have extra rules in my .procmailrc just to weed out
those, but this is a never ending battle as long as spam is legal.

clemens