Ortmann, Chris (TIFPC) wrote:
> I find myself unable to REM0VE myself from this list :-/
>
> Tried logging in at the linux-mandrake website but it tells
> me my email address isn't regstered, go figure.
>
> Anyhow, the list management via e-mail commands don't work
> correctly, one of the addresses you're directed to for list
> support even causes a bounce.
>
> Here's hoping this list is moderated email by email!
>
> -Chris
>
> Below is a snip of the email I keep getting.  sympa doesn't
> exist, and mails sent to sympa-request have gone unanswered
> in over a week.
>
> ===========================================================
>=== If your message effectively contained a command, please
> notice that commands should never ever be sent to lists.
> Commands must be sent to [EMAIL PROTECTED]
> exclusively.
>
> If your message was effectively addressed to the list, it
> has been interpreted by the software as a command. Please
> contact the manager of the service :
> [EMAIL PROTECTED] so that they can take care
> of your message.
> ===========================================================
>===
User commands

    HELP

    Provides the instructions for use of Sympa commands. The result is the content of 
the
    ~sympa/expl/helpfile file. You will find an example of this file in the sample/ 
directory of the distribution.

    INFO listname

    Provides the welcome message for the specified list. The result is the content of 
the ~welcome[.mime].

    LISTS

    Provides the names of lists managed by Sympa. This list can either be generated 
dynamically, using
    visibility (see 8.1.2, page ) and subject list parameters (8.1.1, page ) but also
    ~sympa/expl/lists.header and ~sympa/expl/lists.footer). It can also be generated 
statically by
    including contents of the ~sympa/expl/lists file, which must be updated manually 
by the robot administrator.

    REVIEW listname 

    Provides the parameters of the specified list (owner, subscription mode, etc.), as 
well as the addresses of
    subscribers if the run mode authorizes it. See the review parameter (8.3.7, page ) 
for the configuration file of
    each list, which controls consultation authorizations for the subscriber list. 
Since subscriber addresses can be
    abused by spammers, it is strongly advised to only authorize owners to access the 
susbcriber list.

    WHICH

    Returns the list of lists to which one is subscribed, as well as the configuration 
of his or her subscription to each of
    the lists (DIGEST, NOMAIL, CONCEAL).

    STATS listname 

    Provides statistics for the specified list: number of messages received, number of 
messages sent, mega-bytes
    received, mega-bytes sent. This is the contents of the ~sympa/expl/stats file

    INDEX listname

    Provides index of archives for specified list. Access rights to this function are 
the same as for the GET command. 

    GET listname archive

    To retrieve archives for list (see above). Access rights are the same as for the 
REVIEW command. See review
    parameter (8.3.7, page ).

    LAST listname

    To receive the last message distributed in a list (see above). Access rights are 
the same as for the GET
    command. 

    SUBSCRIBE listname firstname name 

    Requests sign-up to the specified list. The firstname and name are optional. If 
the list is parameterized with a
    restricted subscription (see subscribe parameter, 8.3.1, page ), this command is 
sent to the list owner for
    approval. 

    INVITE listname user@host name 

    Invite someone to subscribe to the specified list. The name is optional. The 
command is similar to the ADD but the
    specified person is not added to the list but invited to subscribe to it accordind 
to the subscribe parameter,
    8.3.1, page ). 

    SIGNOFF listname [ user@host ] 

    Requests unsubscription from the specified list. SIGNOFF * means unsubscription 
from all lists. 

    SET listname DIGEST 

    Puts the subscriber in digest mode for the listname list. Instead of receiving 
mail from the list in a normal manner,
    the subscriber will periodically receive it in a DIGEST. This DIGEST compiles a 
group of messages from the list,
    using multipart/digest mime format. 

    The sending period for these DIGESTS is regulated by the list owner using the 
digest parameter (see 8.4.7,
    page ). See the SET LISTNAME MAIL command (9.1, page ) and the reception parameter 
(7.5,
    page ). 

    SET listname NOMAIL 

    Puts subscriber in nomail mode for the listname list. This mode is used when a 
subscriber wants to no longer
    receive mail from the list; nevertheless he or she maintains the capability of 
writing in the list. This mode therefore
    prevents the subscriber from unsubscribing and subscribing later on. See the SET 
LISTNAME MAIL command
    (9.1, page ) and the reception (7.5, page ).

    SET listname MAIL

    Puts the subcriber in normal mode (default) for the listname list. This option is 
mainly used to cancel the nomail or
    digest modes. If the subscriber was in nomail mode, he or she will again receive 
mail from the list in a normal
    manner. See the SET LISTNAME NOMAIL command (9.1, page ) and the reception 
parameter (7.5, page
      ). 

    SET listname CONCEAL 

    Puts the subscriber in conceal mode for the listname list. The subscriber will 
then become invisible during REVIEW
    on this list. Only owners will see the whole subscriber list.

    See the SET LISTNAME NOCONCEAL command (9.1, page ) and the visibility parameter 
(8.1.2,
    page ). 

    SET listname NOCONCEAL 

    Puts the subscriber in noconceal mode (default) for listname list. The subscriber 
will then become visible during
    REVIEW of this list. The conceal mode is then cancelled.

    See SET LISTNAME CONCEAL command (9.1, page ) and visibility parameter (8.1.2, 
page ).

    QUIT

    Ends acceptance of commands. This can prove useful when the message contains 
additional lines, as for
    example in the case where a signature is automatically added by the user's 
program. 

    CONFIRM key 

    If the send parameter of a list is set to privatekey, publickey or 
privateorpublickey, messages are
    only distributed in the list after an authentication phase by return mail, using a 
one-time password (numeric key).
    For this authentication, the sender of the message is requested to post the 
``CONFIRM key'' command to Sympa. 

    QUIET 

    This command is used for silent (mute) processing: no performance report is 
returned for commands prefixed with
    QUIET).


Reply via email to