From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: listmaster@delorie.com (Mailing List Processor) Newsgroups: gmane.emacs.bugs,gmane.spam.detected Subject: Re: your LISTSERVE request "indecipherable" Date: Thu, 9 Jan 2003 15:14:43 -0500 Sender: bug-gnu-emacs-bounces+gnu-bug-gnu-emacs=m.gmane.org@gnu.org Message-ID: <200301092014.h09KEht28294@delorie.com> Reply-To: listserv@delorie.com NNTP-Posting-Host: main.gmane.org X-Trace: main.gmane.org 1042145008 18804 80.91.224.249 (9 Jan 2003 20:43:28 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Thu, 9 Jan 2003 20:43:28 +0000 (UTC) Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18WjWP-0004st-00 for ; Thu, 09 Jan 2003 21:43:25 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18WjVg-0004pJ-04 for gnu-bug-gnu-emacs@m.gmane.org; Thu, 09 Jan 2003 15:42:40 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 18Wj7L-0007GI-00 for bug-gnu-emacs@prep.ai.mit.edu; Thu, 09 Jan 2003 15:17:31 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 18Wj64-0006oa-00 for bug-gnu-emacs@prep.ai.mit.edu; Thu, 09 Jan 2003 15:16:23 -0500 Original-Received: from delorie.com ([207.22.48.162]) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18Wj4f-0006Pk-00 for bug-gnu-emacs@prep.ai.mit.edu; Thu, 09 Jan 2003 15:14:45 -0500 Original-Received: (from mailnull@localhost) by delorie.com (8.11.6/8.9.1) id h09KEht28294; Thu, 9 Jan 2003 15:14:43 -0500 Original-To: bug-gnu-emacs@prep.ai.mit.edu X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Bug reports for GNU Emacs, the Swiss army knife of text editors List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: bug-gnu-emacs-bounces+gnu-bug-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.bugs:4167 gmane.spam.detected:134874 X-Report-Unspam: http://unspam.gmane.org/gmane.emacs.bugs:4167 If you have problems with this listserv that you can't resolve and you want to talk to a human about it, send email to dj@delorie.com. You can subscribe or unsubscribe to any of the various mailing lists at delorie.com by sending email to "listserv@delorie.com", like this Unix example: $ Mail listserv@delorie.com Subject: (no subject required) add djgpp ^D To get a list of the groups and their purposes, do like this: $ Mail listserv@delorie.com Subject: (no subject required) longindex ^D Note that the digest groups are purposefully closed to mailings. You may subscribe to them, but you may not send mail to them. The commands understood by the listserv program may be upper or lower case, and are: HELP lists this file. This is also sent whenever a message to listserv is received from which no valid command could be parsed. HELP groupname lists a brief description of the group requested. INDEX lists all the groups available for subscription. LONGINDEX lists all the groups and their descriptions. ADD listname DELETE listname Adds you to or removes you from the given list. DELETE address listname Deletes the given address from the list specified. Mail is sent to the address given to confirm the delete operation. If you omit the 'address' the command will assume the mailbox that is in the From: line of the message. Note that UNSUBSCRIBE is a synonym for DELETE. A command must be the first word on each line in the message. Lines which do not start with a command word are ignored. If no commands were found in the entire message, this help file will be returned to the user. A single message may contain multiple commands; a separate response will be sent for each. Please note that is IS possible to delete someone else's subscription to a mailing list. This facility is provided so that subscribers may alter their own subscriptions from a new or different computer account. There is therefore some potential for abuse; we have chosen to limit this by mailing a confirmation notification of any deletion to the address deleted including a copy of the message which requested the operation. At least you can find out who's doing it to you. Examples: add djgpp delete foo@bar.com djgpp-announce