On Mon, Nov 26, 2001 at 04:27:45PM -0500, Dan Boger wrote: > On Mon, Nov 26, 2001 at 10:21:18PM +0100, Patrik Modesto wrote: > > Hi, > > I often get mail with attachement like this: > > > > begin 666 Studie.doc > > MT,\1X*&Q&N$`````````````````````/@`#`/[_"0`&```````````````! > > M````/P``````````$ ``00````$```#^____`````#X```#_____________ > > M____________________________________________________________ > > > > <snip> > > > > ` > > end > > > > It is sent from MSOE and it looks like that, only when the user forwards > > interesting messages to someone else. When sending new composed mail, > > attachement looks right and is recogniced by mutt. I think, this is not > > a valid form of attachement. > > > > What can be wrong? > > pipe it into uudecode - '|uudecode' should do the trick. I wouldn't be > able to tell you when OE decides to encode an attachment in MIME and > when in UU, but either way is decodable.
It works. Thanks. But one question. Why mutt doesn't recognise it as a regular attachement? Patrik > > HTH :) > > -- > Dan Boger > Linux MVP > brainbench.com >
