xml-dev - How to unsubscribe, etc.

["Paul W. Abrahams" <abrahams@valinet.com>]

As a public service, I'm attaching a message that contains
information on how to unsubscribe from xml-dev, plus other
useful information.

If you've subscribed to the digest, then you need to contact
xml-dev-digest-request rather than xml-dev-request.   As far
as I can tell, the only way to switch from the full list to
the digest, or vice versa,
is to unsubscribe from one and then subscribe to the other
one.   That's a change from the days when these lists were
under the management of majordomo (they no longer are).

Paul Abrahams

---

• From: xml-dev-request@lists.xml.org
• To: abrahams@acm.org
• Date: Mon, 16 Oct 2000 12:06:15 -0400 (EDT)

Your message from abrahams@acm.org was received by:

    xml-dev-request@lists.xml.org

We are an automatic command processor.  We will now begin processing your
message, one line at time.  We will print each line of your message and
follow it by one or more lines telling you whether the line was processed
or not.  Each of our lines will begin with the two characters ">>".
-------------------------------------------------------------------------
------------------------------------------------------------------------
Your message was received by xml-dev-request@lists.xml.org.
We are an automatic elist command server.  This is a help summary.

If you need to contact a person, the elist service manager may be
reached by sending an email message to:

  xml-dev-help@lists.xml.org

We receive messages and expect the content to be lines with commands.
You may send more than one command per message but each command must
appear completely on a line by itself.  If a line ends with a backslash
"\" we will add the next line to it before processing it.  Commands in
the Subject: header are ignored.

There are subscriber commands and elist owner commands.  The subscriber
commands are described first.  A brief explanation of all commands is
included here.  A more detailed explanation is available at:

  http://lists.xml.org/doc/email-manage.html

SUBSCRIBER COMMANDS

The following commands may be sent by anyone to the command server.  The
command will be processed according to how the elist is configured.  You
will always get a reply telling you if a command was processed and what
was done.

  subscribe
  unsubscribe
  confirm
  who
  help

SUBSCRIBE

  The word "subscribe" should appear on a line by itself in the body of
  the message.  By default the address that will be subscribed is
  selected from the first of the following header fields with a value:
  REPLY-TO, FROM, SENDER.

  To subscribe an alternate address, or the address of a third party,
  include it on the line after "subscribe".  Any valid email address may
  be specified, e.g.:

    subscribe abrahams@acm.org

UNSUBSCRIBE

  The word "unsubscribe" should appear on a line by itself in the body
  of the message.  By default the address that will be unsubscribed is
  selected from the first of the following header fields with a value:
  REPLY-TO, FROM, SENDER.

  To unsubscribe an alternate address, or the address of a third party,
  include it on the line after "unsubscribe".  Any valid email address
  may be specified, e.g.:

    unsubscribe abrahams@acm.org

CONFIRM

  The confirm command line is provided to you by the elist command
  server in response to a subscribe or unsubscribe command.  When you
  receive it you must return the entire command line to the elist server
  exactly as it was provided to you.  You may break long lines by
  putting a backslash "\" at the end of the incomplete lines.

  In all cases, the command server will respond to the address in the
  first of the following fields to have a value: REPLY-TO, FROM,
  SENDER.  This reply will indicate the command was received and whether
  or not it was processed.

  If the command was processed a separate message will be sent with the
  results of the command, e.g., in the case of a subscribe command the
  subscriber will be sent a welcome message and in the case of an
  unsubscribe command the subscriber will be sent a good-bye message.

WHO

  The word "who" must appear on a line by itself in the body of the
  message.  If the elist owner permits it a copy of the list of
  subscribers will be returned to you.  If it is not permitted you will
  receive an acknowledgement telling you so.

HELP

  When the word "help" appears on a line by itself you receive this
  message.



ELIST OWNER COMMANDS

The following commands are not created by users.  They are created by
the command server and sent to elist owners when an unauthorized message
is received for distribution.  Although there are many reasons why a
message submitted to an elist is considered unauthorized, it is always a
direct result of how an elist is configured.

The commands are as follows:

  delete
  distribute
  reject
  spam

DELETE

  This command is used to end all processing of a message.  The message
  will be removed from the email queue, it will not be returned to its
  sender, and it will not be distributed to your elist.  See also the
  command reject.

  A representative use of this command is:

      delete yes TOKEN IDENTIFIER

  Note that TOKEN and IDENTIFIER must be replaced by actual values that
  are unique to the message being processed.  The values will have been
  provided to you by the elist command server.  You must supply both the
  command "delete" and the confirmation "yes".

DISTRIBUTE

  This command is used to distribute the message to your elist.  If the
  elist is archived a copy will be put there also.

  A representative use of this command is:

      distribute yes TOKEN IDENTIFIER

  Note that TOKEN and IDENTIFIER must be replaced by actual values that
  are unique to the message being processed.  The values will have been
  provided to you by the elist command server.  You must supply both the
  command "distribute" and the confirmation "yes".

REJECT

  This command is used to reject the distribution of the message and to
  send a message to its sender indicating the message was not authorized
  for distribution.  The message will be removed from the email queue,
  it will be returned to its sender, and it will not be distributed to
  your elist.  See also the command "delete".

  A representative use of this command is:

      reject yes TOKEN IDENTIFIER

  Note that TOKEN and IDENTIFIER must be replaced by actual values that
  are unique to the message being processed.  The values will have been
  provided to you by the elist command server.  You must supply both the
  command "reject" and the confirmation "yes".

SPAM

  This command is used to tell us that you consider the message spam and
  you want us to treat it as such.  The message will be removed from the
  email queue, it will not be returned to its sender, and it will not be
  distributed to your elist.  In addition, the message will be forwarded
  to abuse@elistx.com for processing.

  A representative use of this command is:

      spam yes TOKEN IDENTIFIER

  Note that TOKEN and IDENTIFIER must be replaced by actual values that
  are unique to the message being processed.  The values will have been
  provided to you by the elist command server.  You must supply both the
  command "spam" and the confirmation "yes".
------------------------------------------------------------------------

---