[comp.mail.elm] Re-Mail Facility in ELM

elsn4000@mailszrz.zrz.tu-berlin.de (Frank Elsner) (06/19/91)

Not only for politeness let me say that we are perfectly happy with ELM.
 
But many of our users are missing the possibility to send a mail which was
recorded in the =sent folder again. This may be necessary in case of typing
errors after getting a non-delivery to send the same message with the 
address corrected.
 
Is it possible to implement a command in ELM to support re-sending a recorded 
message. The command should allow for editing of header and body.

Frank Elsner (TUBerlin/ZRZ, Postmaster)

syd@DSI.COM (Syd Weinstein) (06/19/91)

elsn4000@mailszrz.zrz.tu-berlin.de (Frank Elsner) writes:
>Is it possible to implement a command in ELM to support re-sending a recorded 
>message. The command should allow for editing of header and body.
Its not only possible, it looks like it might be a good idea.... We
shall see if there are any takers for 2.4 for it.

For now, a work around that does not allow for editing, is to use the
bounce command.
-- 
=====================================================================
Sydney S. Weinstein, CDP, CCP                   Elm Coordinator
Datacomp Systems, Inc.                          Voice: (215) 947-9900
syd@DSI.COM or dsinc!syd                        FAX:   (215) 938-0235

brenner@husc9.harvard.edu (Steven Brenner) (06/20/91)

In article <1991Jun19.134728.14589@DSI.COM> syd@DSI.COM writes:
>elsn4000@mailszrz.zrz.tu-berlin.de (Frank Elsner) writes:
>>Is it possible to implement a command in ELM to support re-sending a recorded 
>>message. The command should allow for editing of header and body.
>Its not only possible, it looks like it might be a good idea.... We
>shall see if there are any takers for 2.4 for it.
>
>For now, a work around that does not allow for editing, is to use the
>bounce command.

Another work-around is to chose (f)orward message, and chose NOT to
edit the outgoing message.  Then, when given the
(S)end/(F)orget/(H)eaders/etc prompt, chose (E)dit.  Just delete the
old headers, and you're set.

Steven Brenner
brenner@husc.harvard.edu

rdc30@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson) (06/22/91)

In article <1991Jun19.134728.14589@DSI.COM> syd@DSI.COM writes:
>elsn4000@mailszrz.zrz.tu-berlin.de (Frank Elsner) writes:
>>Is it possible to implement a command in ELM to support re-sending a recorded 
>>message. The command should allow for editing of header and body.
>Its not only possible, it looks like it might be a good idea.... We
>shall see if there are any takers for 2.4 for it.
>
>For now, a work around that does not allow for editing, is to use the
>bounce command.
>-- 
and for a workaround that allows full editing (body and headers) use
the forward command, edit the Subject: line when presented and answer y)es
to the question on editing the message.  What more needs to go in 2.4?
Perhaps a re-mail command which dumps you straight into header editing?

-- 
Mike Dobson, Sys Admin for      | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil
nmrdc1.nmrdc.nnmc.navy.mil      | UUCP:   ...uunet!mimsy!nmrdc1!rdc30
AT&T 3B2/600G Sys V R 3.2.2     | BITNET:   dobson@usuhsb or nrd0mxd@vmnmdsc
WIN/TCP for 3B2                 | MCI-Mail: 377-2719 or 0003772719@mcimail.com

woodcock@mentor.cc.purdue.edu (Bruce Sterling Woodcock) (06/22/91)

In article <1991Jun21.172141.26002@nmrdc1.nmrdc.nnmc.navy.mil> rdc30@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson) writes:
>and for a workaround that allows full editing (body and headers) use
>the forward command, edit the Subject: line when presented and answer y)es
>to the question on editing the message.  What more needs to go in 2.4?
>Perhaps a re-mail command which dumps you straight into header editing?

But the fact that you have to re-edit all those darn headers *is* a problem...
and you have to delete all of the "> " or whatever you quote with at the
beginning of the line.  What would really be nice is a simple remail command
that allows editing of the body but does not "quote" the previous mail and
sets the headers properly.

Bruce

-- 
|    woodcock@mentor.cc.purdue.edu    | I can usually be found on a tinymud: |
|       sirbruce@gnu.ai.mit.edu       | Asylum -- ds5000.ecn.uoknor.edu 6250 |
|    sterling@shadowfax.cs.utk.edu    |    CaveMUCK -- piggy.ucsb.edu 2000   |
| sterling@maxwell.physics.purdue.edu |   FurryMUCK -- skid.ps.uci.edu 2323  |

dattier@vpnet.chi.il.us (David W. Tamkin) (06/23/91)

woodcock@mentor.cc.purdue.edu (Bruce Sterling Woodcock) wrote in
<13862@mentor.cc.purdue.edu>:

| But the fact that you have to re-edit all those darn headers *is* a problem...
| and you have to delete all of the "> " or whatever you quote with at the
| beginning of the line.  What would really be nice is a simple remail command
| that allows editing of the body but does not "quote" the previous mail and
| sets the headers properly.

I'm not sure what you mean when you say "sets the headers properly."  That's
rather subjective and varies from use to use.

You can edit the body without having it set off by citation characters if you
use the method an earlier contributor to this thread suggested: f)orward,
say (for now) that you DON'T want to edit the message (that prevents the
insertion of citation characters), and then, when you get to the s)end, e)dit,
h)eaders, or f)orget prompt, it's your chance to select e)dit and make
changes to the body.

David Tamkin  PO Box 7002  Des Plaines IL  60018-7002  dattier@vpnet.chi.il.us
GEnie:D.W.TAMKIN  CIS:73720,1570  MCIMail:426-1818  708 518 6769  312 693 0591

"Parker Lewis Can't Lose" mailing list:
 flamingo-request@esd.sgi.com (reflector)    flamingo-request@mcs.com (digest)

oea@ifi.uio.no (Odd Einar Aurbakken) (06/23/91)

In article <1991Jun22.173105.3478@vpnet.chi.il.us>, dattier@vpnet.chi.il.us 
> I'm not sure what you mean when you say "sets the headers properly."  That's
> rather subjective and varies from use to use.

I think this is what Bruce Sterling Woodcock had i mind, quote from 822:

     4.2.  FORWARDING

          Some systems permit mail recipients to  forward  a  message,
     retaining  the original headers, by adding some new fields.  This
     standard supports such a service, through the "Resent-" prefix to
     field names.

          Whenever the string "Resent-" begins a field name, the field
     has  the  same  semantics as a field whose name does not have the
     prefix.  However, the message is assumed to have  been  forwarded
     by  an original recipient who attached the "Resent-" field.  This
     new field is treated as being more recent  than  the  equivalent,
     original  field.   For  example, the "Resent-From", indicates the
     person that forwarded the message, whereas the "From" field indi-
     cates the original author.

          Use of such precedence  information  depends  upon  partici-
     pants'  communication needs.  For example, this standard does not
     dictate when a "Resent-From:" address should receive replies,  in
     lieu of sending them to the "From:" address.

     Note:  In general, the "Resent-" fields should be treated as con-
            taining  a  set  of information that is independent of the
            set of original fields.  Information for  one  set  should
            not  automatically be taken from the other.  The interpre-
            tation of multiple "Resent-" fields, of the same type,  is
            undefined.

Today there is no way to do this within elm. A command to resend mail
should not alter any headers, just add enough "Resent-" headers to make
sendmail (and others) understand you are resending a message and delete
a few headers ("Status:" and possibly some others).

This is not a difficult command to implement, today I have a smal perl
script to do the job.

-- 
-oea					[Just another dc hacker,]Pq

dattier@vpnet.chi.il.us (David W. Tamkin) (06/24/91)

oea@ifi.uio.no (Odd Einar Aurbakken) wrote in
<1991Jun23.121944.20994@ifi.uio.no>:

| In article <1991Jun22.173105.3478@vpnet.chi.il.us>, [I had written]:
| > I'm not sure what you mean when you say "sets the headers properly."  That's
| > rather subjective and varies from use to use.

| I think this is what Bruce Sterling Woodcock had i mind, quote from 822:

| [citation from RFC822 deleted]

| Today there is no way to do this within elm. A command to resend mail
| should not alter any headers, just add enough "Resent-" headers to make
| sendmail (and others) understand you are resending a message and delete
| a few headers ("Status:" and possibly some others).

Then that is what elm's b)ounce command should do.  F)orward, which lets the
forwarder edit the text, correctly sends the final text out as a new letter
with the forwarder's name as the new sender and should work pretty much as it
does now.

David Tamkin  PO Box 7002  Des Plaines IL  60018-7002  dattier@vpnet.chi.il.us
GEnie:D.W.TAMKIN  CIS:73720,1570  MCIMail:426-1818  708 518 6769  312 693 0591

"Parker Lewis Can't Lose" mailing list:
 flamingo-request@esd.sgi.com (reflector)    flamingo-request@mcs.com (digest)