Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!ucbcad!ucbvax!UTAH-CS.ARPA!cetron
From: cetron@UTAH-CS.ARPA.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: Re: a clarification
Message-ID: <8702251624.AA18802@utah-cs.ARPA>
Date: Wed, 25-Feb-87 11:24:22 EST
Article-I.D.: utah-cs.8702251624.AA18802
Posted: Wed Feb 25 11:24:22 1987
Date-Received: Fri, 27-Feb-87 21:28:01 EST
References: <8702242033.AA21637@ucbarpa.Berkeley.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: utah-cs!cetron (Edward J Cetron)
Distribution: world
Organization: Center for Engineering Design, Univ of Utah
Lines: 21
Approved: tcp-ip@sri-nic.arpa

In article <8702242033.AA21637@ucbarpa.Berkeley.EDU> jordan@UCBARPA.BERKELEY.EDU (Jordan Hayes) writes:
>(glad i put a '?' next to it ...) -- the sndmsg balks stuff is from
>Wollongong's VMS mailer ...
>
>egged-face,
>
>/jordan

	Don't feel quite so bad, the software tools mailer is somewhat similar:

After it receives the 'terminating' <cr><lf>.<cr><lf> it spawns off a subshell
which attempts to send the receive message header information to a mailer
daemon....if the send works (address is valid, header info complete, etc) then
it returns and the SMTP server responds with the OK message.  If not, it sends
the appropriate error code (syntax error in address - see RFC 822, date missing
etc...).  There IS a window where the remote mailer could time out, but to date
I have never seen this actually happen - remember, it is NOT  trying to deliver
the message, just verify the headers and queue it for delivery.....

-ed cetron
cetron@utah-cs.arpa