Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!bonnie!akgua!gatech!seismo!brl-tgr!tgr!JCURRAN%UMASS.BITNET@WISCVM.ARPA
From: JCURRAN%UMASS.BITNET@WISCVM.ARPA
Newsgroups: net.mail.headers
Subject: A suggestion for preventing machine mail loops
Message-ID: <537@brl-tgr.ARPA>
Date: Wed, 11-Dec-85 02:54:11 EST
Article-I.D.: brl-tgr.537
Posted: Wed Dec 11 02:54:11 1985
Date-Received: Fri, 13-Dec-85 07:34:10 EST
Sender: news@brl-tgr.ARPA
Lines: 17


    It occurs to me that the rfc822 document has very good
provisions for handling machine generated mail and preventing
'loops' per se.  In a server or demon, one can simply provide
the following set of fields in a out-going message:

From:  Server-name@node
Sender: Person@node
Reply-to: <>

    In this way, the actual origin is specified, but will never
be used as an address; all errors should be sent to the person
responsible for the server, and any attempts at replies to the
server should be disallowed since the reply-to field is null.

-- John Curran
-- Umass/Amherst