LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Roger Fajman <[log in to unmask]>
Sat, 23 Mar 1991 14:28:01 EST
text/plain (64 lines)
== Forwarded Mail ==
 
To: Request-for-Comments-List:;
Subject: RFC1211 on Problems with Mailing Lists
Date: Fri, 22 Mar 91 15:12:08 PST
From: "Joyce K. Reynolds" <[log in to unmask]>
 
 
A new Request for Comments is now available from the Network Information
Center in the online library at NIC.DDN.MIL.
 
       RFC 1211:
 
        Title:      Problems with the Maintenance of Large Mailing Lists
               Author:     A. Westine and J. Postel
       Mailbox:    [log in to unmask], [log in to unmask]
       Pages:      54
       Characters: 96,167
       Updates/Obsoletes:  none
 
               pathname: RFC:RFC1211.TXT
 
 
This RFC discusses problems with maintaining large mailing lists,
especially the processing of error reports.  This memo provides
information for the Internet community.  It does not specify an
Internet standard.  Distribution of this memo is unlimited.
 
RFCs can be obtained via FTP from NIC.DDN.MIL, with the pathname
RFC:RFCnnnn.TXT (where "nnnn" refers to the number of the RFC).  Login
with FTP, username "anonymous" and password "guest".
 
The NIC also provides an automatic mail service for those sites which
cannot use FTP.  Address the request to [log in to unmask] and in the
subject field of the message indicate the RFC number, as in "Subject:
RFC nnnn".
 
RFCs can also be obtained via FTP from NIS.NSF.NET.  Using FTP, login
with username "anonymous" and password "guest"; then connect to the RFC
directory ("cd RFC").  The file name is of the form RFCnnnn.TXT-1
(where "nnnn" refers to the number of the RFC).
 
The NIS also provides an automatic mail service for those sites which
cannot use FTP.  Address the request to [log in to unmask] and leave
the subject field of the message blank.  The first line of the text of
the message must be "SEND RFCnnnn.TXT-1", where nnnn is replaced by
the RFC number.
 
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [log in to unmask]  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
 
Submissions for Requests for Comments should be sent to
[log in to unmask]  Please consult RFC 1111, "Instructions to RFC
Authors", for further information.
 
Requests to be added to or deleted from this distribution list should
be sent to [log in to unmask]
 
 
Joyce K. Reynolds
USC/Information Sciences Institute

ATOM RSS1 RSS2