You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: manual/admin/list-members.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -18,17 +18,17 @@ We'll first describe the standard way for Sympa to handle list members and owner
18
18
19
19
List members are often named *subscribers* because the default way to become member of a list is to subscribe to it. The subscription action can be performed via any of the three Sympa user interface : mail, web or SOAP. The mail command for subscribing is *SUBSCRIBE,* see ~~[user_commands](../mail-commands.md#user_commands)~~. Subscription feature is available from the list homepage on the web interface, but it requires prior user authentication.
20
20
21
-
The configuration of a list may restrict the right to subscribe to this list (closed, moderated, restricted to certain user categories,...) ; this is configured via [the subscribe list parameter](/gpldoc/man/list_config.5.html#subscribe). [A similar list configuration parameter](/gpldoc/man/list_config.5.html#unsubscribe) defines if list members can unsubscribe from the list. If the subscription process is moderated, then list owners will receive mail notifications for each subscription request; they can then validate the request via either web or mail interfaces of Sympa.
21
+
The configuration of a list may restrict the right to subscribe to this list (closed, moderated, restricted to certain user categories,...) ; this is configured via [the subscribe list parameter](/gpldoc/man/sympa_config.5.html#subscribe). [A similar list configuration parameter](/gpldoc/man/sympa_config.5.html#unsubscribe) defines if list members can unsubscribe from the list. If the subscription process is moderated, then list owners will receive mail notifications for each subscription request; they can then validate the request via either web or mail interfaces of Sympa.
22
22
23
-
List owners can also add list members, though this feature should be used with care since users can easily confuse this with spam. It is easier for a subscriber to unsubscribe if (s)he did subscribe himself. List owners can use the ~~[ADD](../mail-commands.md#owner_commands)~~ mail command or the web interface to add new list members. The default right to add and remove list members is provided to list owners, but this behavior can be customized through the [add](/gpldoc/man/list_config.5.html#add) and [del](/gpldoc/man/list_config.5.html#del) list configuration parameters.
23
+
List owners can also add list members, though this feature should be used with care since users can easily confuse this with spam. It is easier for a subscriber to unsubscribe if (s)he did subscribe himself. List owners can use the ~~[ADD](../mail-commands.md#owner_commands)~~ mail command or the web interface to add new list members. The default right to add and remove list members is provided to list owners, but this behavior can be customized through the [add](/gpldoc/man/sympa_config.5.html#add) and [del](/gpldoc/man/sympa_config.5.html#del) list configuration parameters.
24
24
25
25
Sympa stores the list membership data in its database, in the [`subscriber_table` table](/gpldoc/man/sympa_database.5.html#subscriber_table). Along with the list name and member email addresses, Sympa stores the following informations: user name, date of subscription, date of latest update, visibility option, reception option, selected topics, bouncing informations.
26
26
27
27
### Declaring list owners or moderators
28
28
29
-
A list owner is assigned to a list at the list creation time ; it corresponds to the user who requests the list creation. Additional list owners can later be addded by existing list owners or by the listmaster; this is achieved through the list admin web interface. List owners are defined by the [owner list configuration parameter](/gpldoc/man/list_config.5.html#owner).
29
+
A list owner is assigned to a list at the list creation time ; it corresponds to the user who requests the list creation. Additional list owners can later be addded by existing list owners or by the listmaster; this is achieved through the list admin web interface. List owners are defined by the [owner list configuration parameter](/gpldoc/man/sympa_config.5.html#owner).
30
30
31
-
List moderators are managed the same way, defined by the [`editor` list configuration parameter](/gpldoc/man/list_config.5.html#editor). Note that if no list moderator is defined, then the list owners are taken as defaults for them.
31
+
List moderators are managed the same way, defined by the [`editor` list configuration parameter](/gpldoc/man/sympa_config.5.html#editor). Note that if no list moderator is defined, then the list owners are taken as defaults for them.
32
32
33
33
Sympa defines two profiles for list owners: normal and privileged. Privileged owners have extended privileges, including the right to edit some list configuration parameters; this can be customized through the [`edit_list.conf`](/gpldoc/man/edit_list.conf.5.html) configuration file.
34
34
See also "[List editing](list-creation.md#list-editing)".
Sympa lets you use an external antivirus solution to check incoming mails. In this case you must set the `antivirus_path` and `antivirus_args` configuration parameters (see "[Antivirus plug-in](/gpldoc/man/sympa.conf.5.html#antivirus-plug-in)"). Sympa supports at least following products:
9
+
Sympa lets you use an external antivirus solution to check incoming mails. In this case you must set the `antivirus_path` and `antivirus_args` configuration parameters (see "[Antivirus plug-in](/gpldoc/man/sympa_config.5.html#antivirus-plug-in)"). Sympa supports at least following products:
A mail sent to `[email protected]` will be queued to the [``$SPOOLDIR``](../layout.md#spooldir)`/automatic` spool, defined by the `queueautomatic``sympa.conf` parameter (see [`queueautomatic`](/gpldoc/man/sympa.conf.5.html#queueautomatic)). The mail will first be processed by an instance of the `sympa.pl` process dedicated to automatic list creation, then the mail will be sent to the newly created mailing list.
65
+
A mail sent to `[email protected]` will be queued to the [``$SPOOLDIR``](../layout.md#spooldir)`/automatic` spool, defined by the `queueautomatic``sympa.conf` parameter (see [`queueautomatic`](/gpldoc/man/sympa_config.5.html#queueautomatic)). The mail will first be processed by an instance of the `sympa.pl` process dedicated to automatic list creation, then the mail will be sent to the newly created mailing list.
66
66
67
67
### The sympa-milter solution (with Postfix or Sendmail)
68
68
@@ -257,10 +257,10 @@ Configuring Sympa
257
257
258
258
Now we need to enable automatic list creation in Sympa. To do so, we have to:
259
259
260
-
- set the [`automatic_list_feature`](/gpldoc/man/sympa.conf.5.html#automatic_list_feature) parameter to `on` and define who can create automatic lists via the [`automatic_list_creation`](/gpldoc/man/sympa.conf.5.html#automatic_list_creation) (points to an `automatic_list_creation` scenario);
260
+
- set the [`automatic_list_feature`](/gpldoc/man/sympa_config.5.html#automatic_list_feature) parameter to `on` and define who can create automatic lists via the [`automatic_list_creation`](/gpldoc/man/sympa_config.5.html#automatic_list_creation) (points to an `automatic_list_creation` scenario);
261
261
- set the `queueautomatic``sympa.conf` parameter to the spool location where we want these messages to be stored (it has to be different from the [``$SPOOLDIR``](../layout.md#spooldir)`/msg` spool).
262
262
263
-
You can make Sympa delete automatic lists that were created with zero list members; to do so, you should set the [`automatic_list_removal`](/gpldoc/man/sympa.conf.5.html#automatic_list_removal) parameter to `if_empty`.
263
+
You can make Sympa delete automatic lists that were created with zero list members; to do so, you should set the [`automatic_list_removal`](/gpldoc/man/sympa_config.5.html#automatic_list_removal) parameter to `if_empty`.
0 commit comments