Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!spool.mu.edu!uunet!midway!clout!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.mail.elm
Subject: Re: Hey Syd, here's a couple of ideas!
Message-ID: <1991Jun24.145828.3137@chinet.chi.il.us>
Date: 24 Jun 91 14:58:28 GMT
Article-I.D.: chinet.1991Jun24.145828.3137
References: <1991Jun20.141539.16160@DSI.COM> <1991Jun21.035847.18287@chinet.chi.il.us> <1991Jun21.130158.19374@DSI.COM>
Organization: Chinet - Chicago Public Access UNIX
Lines: 15

In article <1991Jun21.130158.19374@DSI.COM> syd@DSI.COM writes:
>It WILL be in 2.4, and it is one of the things holding
>up 2.4.  Elm will support generation and use of those headers for
>overall message, but not for attachments (in 2.4).  Attachments
>will have to wait for attachment support in Elm.

How about an rn-like pipe-to-process for saving/detaching?  If Elm
itself just observes the "outer" Content-Length: header, it could
pipe the entire message off to another program that would know how
to extract the pieces and interactively prompt for filenames. 
The low-level support is already there for pipe-to-process anyway,
but it would be nice to have a dedicated command for it.

Les Mikesell
  les@chinet.chi.il.us