Great Circle Associates Majordomo-Users
(June 1996)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: Reply-To
From: Richard Pieri <ratinox @ unilab . dfci . harvard . edu>
Date: 30 Jun 1996 17:58:39 -0400
To: Majordomo-users @ GreatCircle . COM
In-reply-to: Jim Dawson's message of Fri, 28 Jun 1996 14:31:09 -0700 (PDT)
References: <Pine.BSD/.3.91.960628142206.27610I-100000@dnacom.com>

-----BEGIN PGP SIGNED MESSAGE-----

>>>>> "JD" == Jim Dawson <jdawson@dnacom.com> writes:

JD> There are several RFCs that augment RFC-822; many dealing with
JD> mailing lists.  Go to http://rs.internic.net and poke around.

Got any specific references?

[...]

JD> Wrong. The 'From' (no colon) field is the envelop, and shows the
JD> address the message is mailed from (list owner for mailing lists);

Actually, no.  The "\nFrom ..." expression is sometimes created by the
delivery agent, specifically the Berkeley mail delivery agent, and
perhaps others.  MMDF does not create this "header"; it uses a string of
^A characters as message delimiters.  It in no way part of RFC-822.

JD> the 'From:' (with colons)

In the context of dealing with RFC-822 and similar documents, when
specifying a header name the colon is usually omitted, because all valid
headers have colons.

JD> field is the address of the person who wrote the message and sent it
JD> to the list for remailing.

Almost.  From specifies who wrote the message, the originator.  It may
or may not be the agent responsible for actually submitting it to the
MTA.  When the agent responsible for doing so is *not* the originator,
the Sender header is generated, and sending agent's mailbox is placed in
this field.

And when the originator desired replies to go someplace other than
himself, he generates a Reply-To header with the mailbox(es) of the
appropriate recipient(s).

JD> The 'Sender:' field also reflects who mailed it (again, the
JD> listowner for mailing lists).

Exactly.  In the caste of Mj lists, Mj resubmits the messages posted to
those lists, thus Mj becomes the sending agent, and it's mailbox gets
put into the Sender header.

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3
Charset: noconv

iQCVAwUBMdb4kJ6VRH7BJMxHAQGNJgQAh+3J5vJW4+RPXKZIwmqO4EfXM47VgKsO
AYvtb/3qavZkx7bQ/1S/NT2sqdi5k3BtAj9VWPOspgYk/IvjzuUsgPvuC0LKkcgH
VW0PGNKNMY9ux3N6P8R9HQa1aSyxyv6gtMyQKfv3voYgS+eJ+TsYsETuyyEamLNT
Uoj8FVmaAmI=
=UCWH
-----END PGP SIGNATURE-----
-- 
Richard Pieri/Information Services \ Climb your way to the top; that's why the
<ratinox@unilab.dfci.harvard.edu>   \ drapes are there. -A cat's guide to life
http://www.dfci.harvard.edu/         \ 


References:
Indexed By Date Previous: Re: Reply-To
From: Patrick Lee <patlee@panix.com>
Next: Re: Reply-To
From: graham@ee.washington.edu (Stephen Graham)
Indexed By Thread Previous: Re: Reply-To
From: Jim Dawson <jdawson@dnacom.com>
Next: Re: Reply-To
From: graham@ee.washington.edu (Stephen Graham)

Google
 
Search Internet Search www.greatcircle.com