[comp.mail.elm] Elm in RN

jfh@netcom.UUCP (Jack Hamilton) (03/02/90)

It doesn't appear possible to use Elm as the mailer for the RN "r"
function.  Elm doesn't have a way to read in the header file that RN
writes.

I'd rather use Elm than the RN mailer.  Am I overlooking something?  If I'm
not, please consider this to be a suggestion.

-- 
Jack Hamilton   
jfh@netcom.com (UUCP)  
netcom!jfh@sun.com (Internet, maybe)  
                                     

scs@iti.org (Steve Simmons) (03/02/90)

jfh@netcom.UUCP (Jack Hamilton) writes:

>It doesn't appear possible to use Elm as the mailer for the RN "r"
>function.  Elm doesn't have a way to read in the header file that RN
>writes.

>I'd rather use Elm than the RN mailer.  Am I overlooking something?  If I'm
>not, please consider this to be a suggestion.

This is a feature, not a bug.  Elm is a user agent, not a transport
agent.  As such, it insulates the user from all those crufty things
like headers, etc.  Rn needs a more primitive ua (like /bin/mail)
or to talk directly to the transport agent.  After all, if rn is
generating all the headers/etc for you, why do you want elm?

jfh@netcom.UUCP (Jack Hamilton) (03/03/90)

In article <5064@itivax.iti.org> scs@iti.org (Steve Simmons) writes:
>jfh@netcom.UUCP (Jack Hamilton) writes:
>
>>I'd rather use Elm than the RN mailer.  Am I overlooking something?  If I'm
>>not, please consider this to be a suggestion.
>
>This is a feature, not a bug.  Elm is a user agent, not a transport
>agent.  As such, it insulates the user from all those crufty things
>like headers, etc.  Rn needs a more primitive ua (like /bin/mail)
>or to talk directly to the transport agent.  After all, if rn is
>generating all the headers/etc for you, why do you want elm?

I want elm to insulate me from from all those crufty things like headers.
I want to be able to use my elm aliases.  I want to be able to modify my
.signature before it goes out, perhaps.  I want to have only one mailer to
deal with, not two.  

Enough reasons?  In any case, I don't see how you can describe the LACK of
an option as a feature, even if it's not a bug.  "Feature" implies
something desirable.  
-- 
Jack Hamilton   
jfh@netcom.com (UUCP)  
netcom!jfh@apple.com (Internet, if you're lucky)

lemke@radius.UUCP (Steve Lemke) (03/08/90)

In article <5064@itivax.iti.org> scs@iti.org (Steve Simmons) writes:
}jfh@netcom.UUCP (Jack Hamilton) writes:
}
}>It doesn't appear possible to use Elm as the mailer for the RN "r"
}>function.  Elm doesn't have a way to read in the header file that RN
}>writes.
}
}>I'd rather use Elm than the RN mailer.  Am I overlooking something?  If I'm
}>not, please consider this to be a suggestion.
}
}This is a feature, not a bug.  Elm is a user agent, not a transport
}agent.  As such, it insulates the user from all those crufty things
}like headers, etc.  Rn needs a more primitive ua (like /bin/mail)
}or to talk directly to the transport agent.  After all, if rn is
                                              ^^^^^^^^^^^^^^^^^^^
}generating all the headers/etc for you, why do you want elm?
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Gee, I'm glad you asked (and I'm glad Steve asked in the first place).

I would like to use elm with rn because then all my replies to messages
on usenet would be saved in my elm "outbox".  Frequently I'll think "Gee,
I know I sent a reply to someone about that, but I don't have a copy of
it anywhere!"  --  If I had used elm through rn, I would have a copy.  I
guess I _could_ cc: myself, but I don't usually think of it.  Perhaps I
could modify the rn code to include a "cc: lemke" line in the reply header.
-- 
----- Steve Lemke, Engineering Quality Assurance, Radius Inc., San Jose -----
----- Reply to: radius!lemke@apple.com    (Coming soon: radius.com ...) -----

alan@oetl.UUCP (Alan Strassberg) (03/10/90)

In article <1249@radius.UUCP> radius!lemke@apple.com writes:
>
>I would like to use elm with rn because then all my replies to messages
>on usenet would be saved in my elm "outbox".  Frequently I'll think "Gee,

	Well, one possibility is: (from rn command line)

	!elm <esc>t

	This has the effect of a shell escape to elm with
	the 'From' line of the header. <esc> above is escape.
	Note: if you use csh you'll need to have
	-ESHELL=/bin/sh in your .rninit file (or csh will try
	to find an event for the !).

	All kinds of wonderful variables are available from
	within rn by this technique. Try !<esc>h right now
	to see the help screen. Example: !<esc>z will tell you
	how many bytes are in this posting.

				alan

-- 
Alan Strassberg             alan@oetl.scf.lockheed.com
(408) 425-6139              ...!uunet!lstc!oetl!alan 

leoh@hardy.hdw.csd.harris.com (Leo Hinds) (03/14/90)

In article <515@oetl1.oetl.UUCP> alan@oetl.UUCP (Alan Strassberg) writes:
>	!elm <esc>t
true ... but that does not "read in" the text of the message being mailed about


leoh@hdw.csd.harris.com         	Leo Hinds       	(305)973-5229
Gfx ... gfx ... :-) whfg orpnhfr V "ebg"grq zl fvtangher svyr lbh guvax V nz n
creireg ?!!!!!!? ... znlor arkg gvzr