From uucpadm@wat.hookup.net Sat Oct 26 23:46:59 1996 Received: from MIT.EDU (PACIFIC-CARRIER-ANNEX.MIT.EDU [18.69.0.28]) by bloom-picayune.MIT.EDU (8.7.6/2.3JIK) with SMTP id XAA14627; Sat, 26 Oct 1996 23:46:57 -0400 Received: from nic.wat.hookup.net by MIT.EDU with SMTP id AA24079; Sat, 26 Oct 96 23:46:28 EDT Received: (uucpadm@localhost) by nic.wat.hookup.net (8.8.0/1.177) id XAA17978; Sat, 26 Oct 1996 23:46:27 -0400 (EDT) Date: Sat, 26 Oct 1996 23:46:27 -0400 (EDT) From: UUCP Administrator Message-Id: <199610270346.XAA17978@nic.wat.hookup.net> To: faq-maintainers-request@MIT.EDU Subject: UUCP notification Message from UUCP on nic Sat Oct 26 23:46:26 1996 UUCP job dweomerCea10 for system dweomer requested by daemon Unable to deliver; will try up to one week The job was queued at 1996-10-23 00:44:48. It is rmail rsr@amthyst.dweomer.org >From MIT.EDU!faq-maintainers-request Wed Oct 23 00:44:46 1996 remote from hookup Received: from MIT.EDU (SOUTH-STATION-ANNEX.MIT.EDU [18.72.1.2]) by nic.wat.hookup.net (8.8.0/1.175) with SMTP id AAA27019 for ; Wed, 23 Oct 1996 00:44:46 -0400 (EDT) Received: from BLOOM-PICAYUNE.MIT.EDU by MIT.EDU with SMTP id AA24049; Wed, 23 Oct 96 00:07:26 EDT Received: (from root@localhost) by bloom-picayune.MIT.EDU (8.7.6/2.3JIK) id AAA19110; Wed, 23 Oct 1996 00:07:22 -0400 Date: Wed, 23 Oct 1996 00:07:22 -0400 Message-Id: <199610230407.AAA19110@bloom-picayune.MIT.EDU> From: news-answers-request@MIT.EDU Reply-To: news-answers-request@MIT.EDU To: faq-maintainers-announce@MIT.EDU Subject: POLICY: faq-maintainers/faq-maintainers-announce FAQ Comment: This message was approved for distribution by Ping Huang. one of the faq-maintainers-announce list maintainers. Subject: Policies for faq-maintainers/faq-maintainers-announce X-Version: $Id: mailing-lists-policy,v 1.29 96/10/07 22:49:27 justom Exp $ Welcome to the faq-maintainers or faq-maintainers-announce mailing list. This document explains the purpose of the lists and some administrative details. In addition to being sent to all new subscribers, it is sent to the lists themselves approximately every ninety days to refresh people's memories. [A recent copy of this document can be obtained via anonymous FTP as rtfm.mit.edu:/pub/faq-maintainers/mailing-lists-policy If you do not have access to anonymous FTP, you can retrieve it by sending email to mail-server@rtfm.mit.edu with the command "send faq-maintainers/mailing-lists-policy" in the message.] ******** How to unsubscribe To unsubscribe from the faq-maintainers mailing list, send email to faq-maintainers-request@consensus.com with the subject "unsubscribe" (without the quotes). Do NOT send email to the list itself asking to be unsubscribed. If you have problems with the list server software, email faq-maintainers-request@mit.edu for help. To unsubscribe from the faq-maintainers-announce mailing list, send email to faq-maintainers-announce-request@mit.edu; it will be read by humans. ******** What are these mailing lists? The faq-maintainers and faq-maintainers-announce lists are primarily intended for discussion among (faq-maintainers), or announcements for (faq-maintainers-announce), people on the net who maintain FAQ (Frequently Asked Questions) or other kinds of periodic informational postings. However, subscribers are not required to maintain FAQs; i.e., anyone interested in issues related to maintaining FAQs is welcome to subscribe. Issues discussed on the faq-maintainers list in the past have included: formatting FAQs; how to handle comments about specific commercial products in FAQs; and using software to assist in the posting and maintenance of FAQ postings. Although a wide variety of topics are discussed, using the list for discussions which do not specifically pertain to FAQ maintenance is discouraged. The maintainers of the list may occasionally request that a discussion be moved elsewhere, when they feel that it has strayed too far from the theme of the list. The faq-maintainers-announce list is for announcements only. For example, announcements which would be appropriate include the creation of a new mirror site from which archived *.answers FAQs can be obtained, or the release of a software tool which is particularly useful for FAQ maintainers. The faq-maintainers-announce mailing list has been moderated since April 1994, to prevent unnecessary traffic which doesn't qualify as announcements. Anything sent to the faq-maintainers-announce list also goes to faq-maintainers. ******** How busy and how large are these lists? The faq-maintainers list has several hundred subscribers. Traffic tends to come in bursts -- it averages 3-4 messages per day, but during a burst there may be as many as several dozen messages within a few hours, and in between such bursts, there may be a week of no messages at all. The faq-maintainers-announce list also has several hundred of its own subscribers; in addition, anything approved for it will by default be sent to the faq-maintainers list as well. Traffic on it is very, very low (e.g., it is not unheard of for six months to pass with no messages sent to the list except for a periodic copy of this document). **** Archives All messages sent to the list after December 31, 1993 are publicly available, since recent changes in our handling of the lists have made it possible for us to offer a public archive. You can access the archives in rtfm.mit.edu:/pub/faq-maintainers via anonymous FTP. See the README file for details on archive format. ******** Where to find help with maintaining a posting This section doesn't really "belong" here, but since the question keeps coming up, perhaps this will help. If you want to ask questions specifically of the moderators of *.answers, please send the question to news-answers-request@mit.edu