Users interact with Sympa, of course, when they send messages to one of the lists, but also indirectly through administrative requests (subscription, list of users, etc.).
This section describes administrative requests, as well as interaction modes in the case of private and moderated lists. Administrative requests are messages whose body contains commands understood by Sympa, one per line. These commands can be indiscriminately placed in the Subject: or in the body of the message. The To: address is generally the Sympadomain alias, although it is also advisable to recognize the listservdomain address.
Example:
From: pda@prism.uvsq.fr To: Sympa@cru.fr LISTS INFO Sympa-users REVIEW Sympa-users QUIT
Most user commands have three-letter abbreviations (e.g. REV instead of REVIEW).
HELP helpfile.tt2 template file.INFO listname ~welcome[.mime].LISTS visibility parameter (see Visibility). The lists.tt2 template defines the message returned by the LISTS command.REVIEW listname WHICH STATS listname stats file. review parameter.INDEX listname GET command.GET listname archive REVIEW command. See the review parameter.LAST listname GET command.SUBSCRIBE listname firstname name INVITE listname user@host name ADD, but the person specified is not added to the list but invited to subscribe to it in accordance with the subscribe parameter.SIGNOFF listname [ user@host ] SIGNOFF * means unsubscription from all lists.SET listname DIGEST SET listname SUMMARY summary mode for the listname list. Instead of receiving email from the list in a normal manner, the subscriber will periodically receive the list of messages. This mode is very close to the DIGEST reception mode, but the subscriber only receives the list of messages. This option is available only if the digest mode is set.SET listname NOMAIL nomail mode for the listname list. This mode is used when a subscriber no longer wants to receive email from the list, but nevertheless wishes to retain the possibility of posting to the list. This mode therefore prevents the subscriber from unsubscribing and subscribing later on. See the SET LISTNAME MAIL command and the reception parameter.SET listname TXT txt mode for the listname list. This mode is used when a subscriber wishes to receive emails sent in both format, txt/html and txt/plain only, in txt/plain format. See the reception parameter.SET listname HTML html mode for the listname list. This mode is used when a subscriber wishes to receive emails sent in both format, txt/html and txt/plain only, in txt/html format. See the reception parameter.SET listname URLIZE urlize mode for the listname list. This mode is used when a subscriber wishes not to receive attached files. The attached files are replaced by a URL leading to the file stored on the list site. See the reception parameter.SET listname NOT_ME not_me mode for the listname list. This mode is used when a subscriber wishes not to receive back the message that he/she has sent to the list. See reception parameter.SET listname MAIL normal mode (default) for the listname list. This option is mainly used to cancel the nomail, summary or digest modes. If the subscriber was in nomail mode, he or she will receive email from the list in a normal manner again. See the SET LISTNAME NOMAIL command and the reception parameter. Moreover, this mode allows message topic subscription (see Message topics).SET listname CONCEAL 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 and the Visibility parameter.SET listname NOCONCEAL noconceal mode (default) for the listname list. The subscriber will then become visible during REVIEW of this list. The conceal mode is therefore cancelled. See the SET LISTNAME CONCEAL command and the Visibility parameter.QUIT CONFIRM key 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 QUIET.Some administrative requests are only available to list owners. They are essential for all procedures in limited access mode, and to perform requests in place of users. These comands are:
ADD listname user@host firstname name SUBSCRIBE. You can avoid user notification by using the QUIET prefix (i.e.: QUIET ADD).DELETE listname user@host SIGNOFF. You can avoid user notification by using the QUIET prefix (i.e.: QUIET DELETE).REMIND listname REMIND is used by list owners in order to send an individual service reminder message to each subscriber. This message is made by parsing the remind.tt2 file.REMIND * REMIND * is used by the listmaster to send to each subscriber of any list a single message with a summary of his/her subscriptions. In this case, the message sent is built by parsing the global_remind.tt2 file. For each list, Sympa tests whether the list is configured as hidden to each subscriber (parameter lparam visibility). By default, the use of this command is restricted to listmasters. Processing may take a lot of time!
These commands can be prefixed with QUIET to indicate processing without acknowledgment of receipt.
If a list is moderated, Sympa only distributes messages enabled by one of its moderators (editors). Moderators have several methods for enabling message distribution, depending on the send parameter.
DISTRIBUTE listname key send parameter of a list is set to editorkey or editorkeyonly, each message queued for moderation is stored in a spool (see queuemod), and linked to a key. The moderator must use this command to enable message distribution.REJECT listname key MODINDEX listname