INSTRUCTION: digestrecp
SYNTAX: digestrecp|friko@mumjiboolean.com
DESCRIPTION:
-Defines a recipient to whom all messages in this room should be sent. This
-is used for "list serve" applications. The difference between listrecps and
-digestrecps is that the latter will have messages embedded inside a message
-sent by the listserver. The message will appear to be sent by the room's
-e-mail address instead of the sender's e-mail address.
-
-
-INSTRUCTION: subpending
-SYNTAX: subpending|friko@mumjiboolean.com|listrecp|A234Z|1234567890|http://foo.com/lists
-"Subscription pending" for the specified address. This means that
-someone has requested to subscribe an e-mail address (in this case,
-friko@mumjiboolean.com) to the list. The third parameter is either "list"
-or "digest" to specify a normal subscription or a digest subscription.
-The fourth parameter is an authentication token which is generated by the server
-and e-mailed to the specified address. When the user comes back and supplies
-this token, the subscription is complete. The fifth parameter is a simple
-timestamp, so that we may purge old records which were never confirmed.
-
-The sixth field is the URL of the web page used to enter the subscription
-request, minus any parameters.
-
-
-INSTRUCTION: unsubpending
-SYNTAX: unsubpending|friko@mumjiboolean.com|A234Z|1234567890|http://foo.com/lists
-Similar to the 'subpending' command, except this one is for unsubscribe
-requests. The same rules apply with regard to the token and the web page.
+As of 2021, this is now an alias for listrecp and may be converted to listrecp
+by the mailing list manager.
INSTRUCTION: participate
projects / citadel.git / blobdiff