On Fri, 21 Jul 89 22:10:25 PST John Halperin (415) 926-2257 said:
 
(Actually >> is Leonard as I recall)...
>> Yep.  Most mailers can implement lists.  So, why do people use
>> LISTSERV lists?  User-initiated subscription/unsubscription, so that
>> it doesn't occupy the listowner's time.  The other consideration,
>> which fewer people are concerned about, even though it's more
>> significant (on Bitnet) is the savings in bandwidth from DISTx.  Every
>> mail expert that I've discussed this with says that LISTSERV's use of
>> "Sender:" is in violation of RFC822.  I like LISTSERV.  I do however
>> think that the "To:" and "Sender:" field usage is not good.  When I
>> receive a posting from a list, that posting is not "To" me, it's "To"
>> the list.  I find "To:  ldw" distracting.
>
>I agree with Leonard's points here, but I suspect there are a lot
>of people who prefer the current LISTSERV practice of using the
>Sender field for the list name.  Eric, would it be feasible in a
>future version of LISTSERV for the list owner to specify whether
>the To or the Sender field is used to carry the list name?
>
>--  John Halperin  <[log in to unmask]>
>    Stanford Linear Accelerator Center
 
 
   Two items.  I don't see how LISTSERV's use of Sender is in violation
of RFC822 AS LONG AS LISTSERV IS RESPONSIBLE FOR WHAT GETS SENT TO THE
SENDER FIELD!   Of course, this assumes the mail software sending the
error mail to the sender field (as it should under RFC822) includes the
original headers...   Not all do that and as has been stated many times
it is possible for creative mail systems to fake out LISTSERV...
I realize there is a strong recommendation that the sender be a human
person, but the definition says it may refer to a person or system or
process.
 
   But to me the RFC822 characterization of "sender" as a "secretary"
sending mail on someone's behalf is really what LISTSERV is doing.
It really uses the "list address" as the "secretaries" name.  I guess
I think of this as virtual servers or something... ;-)   Anyway, I
don't really feel all that strongly about this I guess.
 
   A LONG time ago (not sure when) Eric added a Sender keyword to LISTSERV.
You specify it as in   Sender= Sucker@somenode  .  However, as I recall
Eric warned people that they were on their own if they caused a meltdown
of the world network by using this...  ;-)
 
   Be aware that if you DO try this, that address will get sent many
messages from mailer about where each item of mail was sent.  I would
suggest you not make it the ID of anyone trying to do any work.  And
they will receive the error bounces from most mail systems (except
those that insist on sending them to the From: or Reply-To: address).
Crosswell mailer will also send the recipient a message saying the mail
is from whatever address you put in Sender.
 
   Anyway, I would use a bit of caution before you rush in to change your
lists!   The To: address may not be such a bit deal since many subscribers
of distributed lists are now receiving their mail with
To:  Multiple Recipients of list xxxxx <xxxxx@yyyyy>
anyway.
 
         Marty