| 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.
the | uuencode cmd line work fine ...
so it can
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 transl
Chris Fuchs, 2001-Jul-31 07:53 -0700:
> on Tue,31 Jul 2001, R. Leponce wrote:
>
> > 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 lik
on Tue,31 Jul 2001, R. Leponce wrote:
> 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 ??
Work
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 pipi
