Re: Strange attachement
On 2001-11-26 17:54:31 -0500, Louis LeBlanc wrote: From the index, '.d' causes the entire message to be piped thru uudecode which will try to decode all encoded attachments. This probably depends on the particular uudecode implementation you are using... I've seen uudecode only decode the _first_ attachment. As an alternative, you could pipe the message through uudeview(1), which will nicely handle multiple uuencoded files in a single message, and even ask you which ones you want to decode. -- Thomas Roesslerhttp://log.does-not-exist.org/ msg20720/pgp1.pgp Description: PGP signature
Re: Strange attachement
On 2001.11.27, in [EMAIL PROTECTED], Thomas Roessler [EMAIL PROTECTED] wrote: This probably depends on the particular uudecode implementation you are using... I've seen uudecode only decode the _first_ attachment. Some uudecodes even choke if there's any material in the input stream before the begin line. These wouldn't accept a full mail message very nicely. OTOH, it's been a long time since I noticed one of these; maybe they're all extinct. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Strange attachement
On 11/27/01 11:23 AM, David Champion sat at the `puter and typed: On 2001.11.27, in [EMAIL PROTECTED], Thomas Roessler [EMAIL PROTECTED] wrote: This probably depends on the particular uudecode implementation you are using... I've seen uudecode only decode the _first_ attachment. Some uudecodes even choke if there's any material in the input stream before the begin line. These wouldn't accept a full mail message very nicely. OTOH, it's been a long time since I noticed one of these; maybe they're all extinct. From uudecode(1) on FreeBSD: . . . Uudecode transforms uuencoded files (or by default, the standard input) into the original form. The resulting file is named name and will have the mode of the original file except that setuid and execute bits are not retained. Uudecode ignores any leading and trailing lines. The following options are available for uudecode: -c Decode more than one uuencode'd file from file if possible. -i Do not overwrite files. -p Decode file and write output to standard output. -s Do not strip output pathname to base filename. By default uudecode deletes any prefix ending with the last slash '/' for security purpose. . . . So this version will ignore leading and trailing data, and the -c flag I used in my example will tell it to decode multiple encoded files if possible. uudeview is another option, as Thomas pointed out, I've used this when downloading Loony Toons and old Betty Boop cartoons from newsgroups. Just tag all the messages, save them all to a single file. Then, from the command line, uudeview will sort them, attach parts, and save the decoded portions. I haven't figured out wether it's better to use this for my email decodings, tho. YMMV HTH Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ Hitchcock's Staple Principle: The stapler runs out of staples only while you are trying to staple something. msg20727/pgp0.pgp Description: PGP signature
Strange attachement
Hi, I often get mail with attachement like this: begin 666 Studie.doc MT,\1X*QN$`/@`#`/[_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? Thanks. Patrik
Re: Strange attachement
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*QN$`/@`#`/[_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. HTH :) -- Dan Boger Linux MVP brainbench.com msg20702/pgp0.pgp Description: PGP signature
Re: Strange attachement
On 11/26/01 10:21 PM, Patrik Modesto sat at the `puter and typed: Hi, I often get mail with attachement like this: begin 666 Studie.doc MT,\1X*QN$`/@`#`/[_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? Looks like a M$ Word attachment. You have to edit the mailcap file and tell it how to handle these attachments. You might want to take a look at third party apps for Mutt (look in the archives, or maybe someone can repost the URI? I don't remember it offhand). At the mutt page, you can take a look at mutt pages by mutt users. There are lots of very cool things you can do to have almost any kind of attachment handled and viewable automatically - if you want. Mutt will do most anything you need or want it to do, but the front end work can be a long process. Get using it, and find out how to solve each problem when it gets to the point where it's worth the while to search mutt.org and the list, etc. I don't think I can ever use another MUA, but I still haven't gotten all the rough edges smoothed out completely. BTW, if you want to view Word Docs inline, there are useful links directly from Mutt regarding configuration. The 3rd party app you want is wv, I think. Used to be wordview, but it changed a while back. HTH Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ Steinbach's Guideline for Systems Programming: Never test for an error condition you don't know how to handle. msg20703/pgp0.pgp Description: PGP signature
Re: Strange attachement
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*QN$`/@`#`/[_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
Re: Strange attachement
On Mon, Nov 26, 2001 at 04:33:39PM -0500, Louis LeBlanc wrote: On 11/26/01 10:21 PM, Patrik Modesto sat at the `puter and typed: Hi, I often get mail with attachement like this: begin 666 Studie.doc MT,\1X*QN$`/@`#`/[_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? Looks like a M$ Word attachment. You have to edit the mailcap file and tell it how to handle these attachments. You might want to take a look But this attachment doesn't have any application/... signature. It is completely inline. What line should I add in mailcap? at third party apps for Mutt (look in the archives, or maybe someone can repost the URI? I don't remember it offhand). At the mutt page, you can take a look at mutt pages by mutt users. There are lots of very cool things you can do to have almost any kind of attachment handled and viewable automatically - if you want. Mutt will do most anything you need or want it to do, but the front end work can be a long process. Get using it, and find out how to solve each problem when it gets to the point where it's worth the while to search mutt.org and the list, etc. I don't think I can ever use another MUA, but I still haven't gotten all the rough edges smoothed out completely. BTW, if you want to view Word Docs inline, there are useful links directly from Mutt regarding configuration. The 3rd party app you want is wv, I think. Used to be wordview, but it changed a while back. No. I don't want to view MS word document inline. It could by nice to show this file in attachments submenu, for easy saving. Patrik HTH Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org Steinbach's Guideline for Systems Programming: Never test for an error condition you don't know how to handle.
Re: Strange attachement
On 011126, at 23:02:16, Patrik Modesto wrote On Mon, Nov 26, 2001 at 04:33:39PM -0500, Louis LeBlanc wrote: On 11/26/01 10:21 PM, Patrik Modesto sat at the `puter and typed: I often get mail with attachement like this: begin 666 Studie.doc MT,\1X*QN$`/@`#`/[_0! snip ` end It is sent from MSOE ... What can be wrong? Looks like a M$ Word attachment. You have to edit the mailcap file and tell it how to handle these attachments. You might want to take a look But this attachment doesn't have any application/... signature. It is completely inline. What line should I add in mailcap? Do the message headers indicate that it is a multi-part message? If so, there should be a Content-Type header for the attachment. You'll need a mailcap entry to tell it how you want that type decoded. If the headers don't indicate a multi-part message, the attachment hasn't been sent as an attachment and mutt won't recognize it as such. -- David Ellement
Re: Strange attachement
On 11/26/01 11:02 PM, Patrik Modesto sat at the `puter and typed: On Mon, Nov 26, 2001 at 04:33:39PM -0500, Louis LeBlanc wrote: On 11/26/01 10:21 PM, Patrik Modesto sat at the `puter and typed: Hi, I often get mail with attachement like this: begin 666 Studie.doc MT,\1X*QN$`/@`#`/[_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? Looks like a M$ Word attachment. You have to edit the mailcap file and tell it how to handle these attachments. You might want to take a look But this attachment doesn't have any application/... signature. It is completely inline. What line should I add in mailcap? My mistake. Dan was correct. I just saw the name and figured it was a word attachment. You can tie a macro to a keystroke and automatically pipe a message thru uudecode to automagically save those encoded messages. Here is mine: macro attach .d | uudecode -c enter From the index, '.d' causes the entire message to be piped thru uudecode which will try to decode all encoded attachments. HTH Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ Research is the best place to be: you work your buns off, and if it works you're a hero; if it doesn't, well -- nobody else has done it yet either, so you're still a valiant nerd. msg20709/pgp0.pgp Description: PGP signature
Re: Strange attachement
On Mon, Nov 26, 2001 at 02:43:41PM -0800, David Ellement wrote: On 011126, at 23:02:16, Patrik Modesto wrote On Mon, Nov 26, 2001 at 04:33:39PM -0500, Louis LeBlanc wrote: On 11/26/01 10:21 PM, Patrik Modesto sat at the `puter and typed: I often get mail with attachement like this: begin 666 Studie.doc MT,\1X*QN$`/@`#`/[_0! snip ` end It is sent from MSOE ... What can be wrong? Looks like a M$ Word attachment. You have to edit the mailcap file and tell it how to handle these attachments. You might want to take a look But this attachment doesn't have any application/... signature. It is completely inline. What line should I add in mailcap? Do the message headers indicate that it is a multi-part message? If so, there should be a Content-Type header for the attachment. You'll need a mailcap entry to tell it how you want that type decoded. If the headers don't indicate a multi-part message, the attachment hasn't been sent as an attachment and mutt won't recognize it as such. There is no Content-Type header. There is: few times Received: from From, To, Subject, Date fields X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Return-Path: -removed/private- X-Orcpt: rfc822;[EMAIL PROTECTED] Status: RO Content-Length: 48003 Lines: 781 then few empty lines and then the encoded file above. I can get to the PC that sends this attachments so I will check it's MSOE setup. Thanks. Patrik
Re: Strange attachement
On 2001.11.26, in [EMAIL PROTECTED], Patrik Modesto [EMAIL PROTECTED] wrote: There is no Content-Type header. There is: ... then few empty lines and then the encoded file above. I can get to the PC that sends this attachments so I will check it's MSOE setup. It's not naturally MIME, but if you can always assume that uuencoded content from MSOE is supposed to be an attached document, you can probably fake something up with procmail. Something like this: :0 fBH * X-Mailer: Microsoft Outlook Express * ^begin [0-7][0-7][0-7] [A-Za-z0-9] | formail -I Content-Type: application/octet-stream \ -I Content-Transfer-Encoding: x-uuencode That should make it a document containing one inline component that mutt can decode and view using whatever your application/octet-stream viewer is. (By default, mutt tries to treat it as text.) With a slightly fancier bit of scripting, you could extract the filename from the begin line, and add that to the MIME description, and you could ensure that ONLY uuencoded material was processed, and make it attached instead of inline... etc. But this should suit your most fundamental need. The MIME isn't exactly perfect, but it's sufficient for this sole purpose. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Strange attachement
Patrik -- ...and then Patrik Modesto said... % 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: % % begin 666 Studie.doc ... % end % ... % 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? Because it's not attached per se, with a MIME header structure and a proper Content-Type: and so on. uuencoding is how computers used to send binary data back and forth, particularly through email (though also commonly through news), and all of this automatic viewing and decoding stuff hadn't yet been invented :-) David Champion's suggestion about playing with the headers is probably the best way to go about making these attachments appear automatically, other than finding whoever uses LookOut! and LARTing him :-) % % Patrik HTH HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg20716/pgp0.pgp Description: PGP signature
Re: Strange attachement
On Mon, Nov 26, 2001 at 10:45:02PM +0100, Patrik Modesto wrote: It works. Thanks. But one question. Why mutt doesn't recognise it as a regular attachement? Because it isn't an attachment. It's part of the message body. Just text. That's how you did it before MIME. ^_^ -- Marc Wilson [EMAIL PROTECTED] [EMAIL PROTECTED] msg20718/pgp0.pgp Description: PGP signature
