Article View: comp.mail.elm
Article #3574Re: Tag and uuencoded files
From: chris
Date: Wed, 27 Jan 1993 17:54
Date: Wed, 27 Jan 1993 17:54
41 lines
2693 bytes
2693 bytes
/* Written 11:30 pm Jan 23, 1993 by dattier@ddsw1.UUCP in tisdec.tis.tandy.com:comp.mail.elm */ First, there should be no need to uudecode the files in any particular order. The "begin" header of a uuencode gives the name that the uudecoded file will have, and if the uuencodes were part of a single distribution every single one will have a unique name in its "begin" header for the uudecoded version of its own contents. Second, tagging and piping won't work with uudecode. It's not Elm's fault: it's uudecode's problem. If you tag and pipe, Elm assembles a text of all tagged messages (in the order of the current display) separated by a row of hyphens between each two messages and pipes that to one invocation of the program you specify. uudecode sees the "end" directive at the bottom of the first message, exits, and ignores the rest of the pipe. There is no provision in the uuencode standard for "next" or "continue" to mean 'close off the file you've been writing but look for another file's "begin" line coming up.' formail, which is part of the procmail distribution, can split up a pipe or an input file into separate messages. I take care of the task by tagging the messages and piping them to formail -s uudecode. David W. Tamkin Box 59297 Northtown Station, Illinois 60659-0297 dattier@ddsw1.mcs.com CompuServe: 73720,1570 MCI Mail: 426-1818 /* End of text from tisdec.tis.tandy.com:comp.mail.elm */ Well, what about those of US that use FTPMail servers. MOST of these servers will uuencode the request, and then split the uuencoded file into managable (~64k) chunks. (Like ftpmail@dewrl.dec.com) From your 'Second' statement it _IS_ Elm's fault for sticking in the row of hyphens between messages. Also if you CANNOT specify an order to pipe taged messages, it is still Elm's fault (or is there a way to order the current display???). I guese the QUESTION should be asked - Why is there no provision provided in Elm to work with UUENCODE, and mail servers in particular? =============== Chris Riney chrisr@Jaoom.LoneStar.ORG ...!jasoom.lonestar.org!chrisr An Elm soon-to-be rookie novice.
Technical Details
Message-ID:
<9800001@tisdec.tis.tandy.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!charon.amdahl.com!amdahl!rtech!pacbell.com!ames!sun-barr!cs.utexas.edu!convex!news.oc.com!utacfd.uta.edu!trsvax!trsvax!tisdec.tis.tandy.com!chrisReferences:
<4@<C1CFAo>Show Full Headers
Complete Article Headers
From: chris@tisdec.tis.tandy.com Date: 27 Jan 93 11:54 CST Newsgroups: comp.mail.elm Subject: Re: Tag and uuencoded files Message-ID: <9800001@tisdec.tis.tandy.com> Path: arc1-ca.pugleaf.net!sparky!uunet!charon.amdahl.com!amdahl!rtech!pacbell.com!ames!sun-barr!cs.utexas.edu!convex!news.oc.com!utacfd.uta.edu!trsvax!trsvax!tisdec.tis.tandy.com!chris Nf-ID: #R:<C1CFAo:4:tisdec.tis.tandy.com:9800001:000:2157 Nf-From: tisdec.tis.tandy.com!chris Jan 27 11:54:00 1993 References: <4@<C1CFAo> Lines: 42