Mailing List Server Overview
In AXIGEN, the integrated list server provides advanced mailing lists administration options. For each list, advanced parameters allow administrators to specify:

• AXIGEN services running, content type, what messages are moderated messages, what headers to remove etc.
• WebMail specific settings allow configuring the way mail lists are viewed and managed on the Web (see Mailing List WebMail Options).

The AXIGEN List Server also provides RFC compliant templates / macros for automated mailing list interaction which allow you to add header text and other types of text before and after the message body.

For each list, standard text messages can be specified to be returned in the following cases: invalid user name, unknown user, request needs confirmation, user already subscribed, rejected response, welcome text, goodbye text, subscribe denied, etc.
All these advanced parameters guarantee easy list administration and easily definable custom appearance and behavior for each list. For information how to configure list parameters, see the Mailing Lists Tab.

Administration of the Mail List

The current version of AXIGEN Mail Server does not differentiate, from an operational point of view, a list administrator from a list moderator. This operational difference will be featured in a next version of AXIGEN Mail Server. Therefore, currently the person who creates the mail list will act as both administrator and moderator of the list created.
Also, please note that, list users are distinct from user mailboxes, even if both entities are administered using AXIGEN Mail Server.

Message Flow for AXIGEN List Server

From the moderator / administrator point of view, the folders below describe the flow for a message sent to a list managed with AXIGEN Mail Server:

• INBOX: stores all messages that have been already delivered are to be delivered.
• PendingRequests: stores all the requests that have to be confirmed by the administrator. The administrator can confirm a message in this folder by moving it to ConfirmedRequests.
• Requests: stores all requests that need to be confirmed by their senders (for instance subscription requests). When such a confirmation is received and verified, the request is moved to ConfirmedRequests.
• ConfirmedRequests: stores all requests confirmed by their senders.
• Pending: stores all messages that need to be moderated. The moderation is executed by moving the corresponding message to:

1. INBOX (the message will be published)
2. Reject (the message is automatically rejected),
3. ToBeRejected (the message is stored for a future manual reject)

• Reject: When a message arrives in this folder, the sender of the message receives a reject message and the original message is moved to Deleted.
• ToBeRejected: stores messages that need to be manually rejected by one of the list moderators.
• Deleted: Here are stored all messages that have been rejected by list moderators.

From the mail list user point of view:
A mail list user would interact with the list in different stages: when subscribing to the mail list, when confirming his/her subscription, when making a request, when accessing the list WebMail page or root mailbox, etc. The answers received from the list server are generated automatically, depending on the initial configuration of the mail list (done by the administrator) and the administrator's corresponding actions.

Templates explained

From a mail list administrator/moderator point of view, most of the messages send as answers on a mail list created and operated with AXIGEN Mail Server are in fact expanded macros or templates.

All macros have the following form:
%[-][width][.precision]{macro letter}
Here is the algorithm used when expanding these macros:
len = strlen(macro text);
width default = 0;
precision default = INT_MAX;
left pading default = false;

if minus => left pading = true;

precision = min (len, precision);
pading = max (0, min(512, pading - precision));

if left pading => the trailing spaces are inserted before macro text ;
if not => the trailing spaces are inserted after the macro text;

Here is the list of macro letters and their meanings:

• l - Name of the list
• d - The domain name of the list.
• r -  A short description of the list.
• o  - Operation to be executed (this option is valid only for the answers sent to requests).
• e  - Address of the original message sender.
• i  - Identity confirmation. This is a message in the following format: "confirm {ID message} {random number}" Note that this option can also be used as a boundary when building multipart messages.
• x - Row
• M - Original message (populated only for answers to automatically rejected messages.
• f - Sender of the message (can be either a name or an e-mail address).
• w - Original message date.
• s - Original message subject.
• m - Original Message ID
• n - The number of the digest message.

For detailed information on how to configure mail lists in WebAdmin, see Mailing Lists
Lists can also be configures using CLI - see Configuring AXIGEN using CLI.