If Cris' suggestion doesn't solve the whole problem, try it from the
attachment menu - v from the index, highlight the uuencoded
attachment, then use the "| uudecode -P . . ." whatever. This should
avoid any conflict with the mail headers.
Another idea, since you are using procmail, is to translate on the
fly. You would have to study that and come up with a very careful
recipe, but the procmail list users can probably help.
HTH
L
On 07/31/01 10:48 AM, R. Leponce sat at the `puter and typed:
> Hi all,
>
> I know this question has been sent many time on the mutt-user ML but I'm so
> tired of browsing and browsing and browsing the archives for a minor pb.
>
> Sometimes I receive uuencoded attachement within the message body and mutt
> seems to be unable to decode it itself (begin ... end). And piping this
> message to the uudecode cmd line does not works (don't like email header
> ??).
>
> Any solution ??
>
> FYI I'm using Mutt w/ Procmail
>
> Thanks in advance.
>
> R.
>
--
Louis LeBlanc [EMAIL PROTECTED]
Fully Funded Hobbyist, KeySlapper Extrordinaire :)
http://acadia.ne.mediaone.net ԿԬ
It seems intuitively obvious to me, which means that it might be wrong.
-- Chris Torek
