[23] in Zephyr Mailing List
mailing list troubles
daemon@ATHENA.MIT.EDU (Ken Raeburn)
Sat Sep 8 15:23:31 1990
Date: Sat, 8 Sep 90 15:15:45 -0400
From: Ken Raeburn <Raeburn@MIT.Edu>
To: zephyr@ATHENA.MIT.EDU
A few people seem to have been getting mail from this list when they
shouldn't have. I don't know how this happened, but am investigating.
Since I have taken over this project, I have added no one to this list
who hasn't asked to be put on it.
If you do not wish to be on this list, please send mail to
zephyr-request@mit.edu, not to zephyr@mit.edu. The "-request"
convention is fairly standard for Internet mailing lists, and prevents
administrative requests from being rebroadcast to widely-distributed
lists. (A couple of sites appear to have redistribution lists; I
assume that you'll know if you're on one of those.)
I repeat here a message John Kohl sent to this list a year ago:
----------------
You are getting this mail because at some point you expressed interest
in the Zephyr Notification Service developed at MIT Project Athena.
This mailing list is intended for general questions, discussion, etc.
about Zephyr.
To mail to the zephyr mailing list, send mail to zephyr@athena.mit.edu;
send administrivia (additions, deletions) to zephyr-request@athena.mit.edu
[This is analogous to the set-up of the kerberos@athena.mit.edu mailing
list].
You should have received an announcement of how to get the sources to
zephyr in the last week (unless you are an Athenian). If you did not,
and you would like information, please send mail to
zephyr-request@athena.mit.edu.
----------------
(Athena.MIT.EDU and MIT.EDU are functionally equivalent mail hosts.)
If you use the Discuss conferencing system, developed by the MIT
Student Information Processing Board, you can also access this list
with the Discuss command
add_meeting menelaus.mit.edu:/usr/spool/discuss/zephyr_mail
This meeting is also an archive of this list.
For those who are wondering, I hope to get out a new set of sources
sometime this month. This should include bug fixes and porting
changes that have been sent to us, and a more efficient server.
-- Ken Raeburn
Zephyr project leader
