Article View: net.mail.headers
Article #54automatic generation of replies
From: Local
Date: Wed, 11 Dec 1985 16:57
Date: Wed, 11 Dec 1985 16:57
26 lines
1583 bytes
1583 bytes
I don't think that rfc822 CLEARLY pointed out that
automatically generated replies should have a "return-path" of
null. In fact, rfc822 discusses computer generated messages and
states that since computer programs cannot be held accountable,
the SENDER field of the message should contain an path of the
human responsible. This means that a good header specification
resulting from a demon could be:
From: Demon@Node...
Sender: Demon-fixers@node..
By rfc822, Demon-fixers will recieve "notices of any
problems in transport or delivery of the original messages"
while Demon@node will recieve any replies. This works very well
except when the server/demon doesn't want any replies sent to
it. It can either discard them as the arrive, or since a
REPLY-TO field is the address that "the reply should go to..
and not the FROM field" the demon could simply indicate on its
messages that it does not wish replies (of any kind, automatic
or 'real') by including a REPLY-TO field of Null.
Comments?
-- John Curran
-- Umass/Amherst
Technical Details
Message-ID:
<571@brl-tgr.ARPA>Path:
arc1-ca.pugleaf.net!utzoo!watmath!clyde!bonnie!akgua!gatech!seismo!brl-tgr!tgr!Local UMass address is\@Show Full Headers
Complete Article Headers
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: arc1-ca.pugleaf.net!utzoo!watmath!clyde!bonnie!akgua!gatech!seismo!brl-tgr!tgr!Local UMass address is\@ From: Local@tgr.UUCP Newsgroups: net.mail.headers Subject: automatic generation of replies Message-ID: <571@brl-tgr.ARPA> Date: Wed, 11-Dec-85 11:57:31 EST Article-I.D.: brl-tgr.571 Posted: Wed Dec 11 11:57:31 1985 Date-Received: Sat, 14-Dec-85 00:37:35 EST Sender: news@brl-tgr.ARPA Lines: 26