This example will discuss an example of a somewhat restricted list. Subscription requests are referred to a list owner. Only members of the list may post directly to the list; if others attempt to post, their postings will be referred to the list owner. Such a list definition in the PMDF alias file might be:
group-list: group-list-expand@process group-list-expand: <PMDF_MAILSERV_MAIL_DIR:group-list.dis, \ [MODERATOR_ADDRESS] group-list-owner@acme.com, \ [MODERATOR_LIST] PMDF_MAILSERV_MAIL_DIR:group-list.dis, \ [USERNAME] group-list-owner, \ [HEADER_ADDITION] PMDF_TABLE:group-list-headers.txt, \ group-list-owner@acme.com, \ group-list@acme.com group-list-request: MAILSERVBecause the entire list is used for the [MODERATOR_LIST] argument, anyone already on the list may post directly to the list. But attempted postings from anyone else will be referred to the [MODERATOR_ADDRESS] argument, group-list-owner@acme.com.
The above list definition references a file of headers to be added to messages posted to the list; such a file might be:
List-Help: <mailto:mailserv@acme.com?body=help> (MAILSERV Instructions), <mailto:group-list-owner@acme.com?subject=help> (List Manager) List-Subscribe: <mailto:group-list-owner@acme.com?subject=subscribe%20group-list> List-Unsubscribe: <mailto:mailserv@acme.com?body=unsubscribe%20group-list> List-Post: <mailto:group-list-owner@acme.com> (List Moderator) List-Owner: <mailto:group-list-owner@acme.com?Subject=group-list>
Only group-list-owner@acme.com will be permitted to subscribe users to the list. group-list-owner may also unsubscribe other users from the list. And group-list-owner@acme.com will have to confirm any SUBSCRIBE or UNSUBSCRIBE commands; that is, when group-list-owner@acme.com sends a SUBSCRIBE or UNSUBSCRIBE request to MAILSERV, MAILSERV will send back to group-list-owner@acme.com a message containing a cookie string, which group-list-owner@acme.com will need to include in a second, confirming message in order for the command to actually be performed. Users may unsubscribe themselves, but attempts to unsubscribe others will be referred to the group-list-owner. Only members of the list will be permitted to request the list membership file, and MAILSERV will require that such requests be confirmed with a second request message including a cookie string that MAILSERV sends out to the supposed requestor address.
MAILSERV_ACCESS SUBSCRIBE|group-list|group-list-owner@acme.com|* $K$V$Y (1) SUBSCRIBE|group-list|group-list-owner@acme.com $K$Y (2) SUBSCRIBE|group-list|*|* $*group-list-owner@acme.com (3) SUBSCRIBE|group-list|* $*group-list-owner@acme.com (4) UNSUBSCRIBE|group-list|group-list-owner@acme.com|* $K$V$Y (5) UNSUBSCRIBE|group-list|group-list-owner@acme.com $K$Y (6) UNSUBSCRIBE|group-list|*|* $Y$*group-list-owner@acme.com (7) UNSUBSCRIBE|group-list|* $Y (8) SENDLIST|group-list|group-list-owner@acme.com $Y (9) SENDLIST|group-list|* $X$<PMDF_MAILSERV_MAIL_DIR:group-list.dis (10) PURGELIST|group-list|group-list-owner@acme.com $Y (11) MAILSERV_LISTS group-list $Agroup-list-owner@acme.com (12)
More specifically: