Purpose: Controls whether posters receive automatic "your message has been accepted" acknowledgments.

Typical values:

Ack= Yes
Ack= No

Common use:

• Yes – Useful for low-volume lists or when senders need assurance their message was processed.
• No – Reduces message traffic on busy lists.

Purpose: Used in ISP scenarios to control insertion of advertising or sponsor footers in messages.

Note: Typically only used in commercial/ISP environments; many institutional deployments leave this at default or disabled.

Purpose: Controls whether and how attachments are allowed on the list.

Typical values:

Attachments= No
Attachments= Yes

Common use: Many sites set No for security and compliance reasons, forcing links instead of attached files.

Purpose: Controls automatic deletion of subscribers whose addresses generate repeated delivery errors.

Typical value (simplified):

Auto-Delete= Yes

Meaning: LISTSERV monitors bounces and may automatically remove subscribers whose addresses appear to be permanently bad, reducing wasted mail and resource usage.

Purpose: Controls automatic backup of the list definition and/or membership.

Use: Many sites instead rely on filesystem or VM-level backups; this keyword is not always used explicitly.

Purpose: Assigns the list to one or more categories for searching in CataList (the LISTSERV list catalog).

Typical value:

Categories= Education,Alumni

Meaning: Helps users discover the list when browsing or searching the public catalog.

Purpose: Enables detailed logging of subscription changes, postings, and related events for the list.

Typical values:

Change-Log= Yes,Monthly
Change-Log= Yes,Daily

Meaning: When enabled, LISTSERV writes events to listname.CHANGELOG files, which can be used for statistics, audits, and reporting.

Common use: Recommended for important lists where you may later need metrics (posts per user, subscriber churn, etc.).

Purpose: Controls whether the list appears in public catalogs (e.g., CataList) or is hidden.

Typical values:

Confidential= No
Confidential= Yes
Confidential= Service

Value meanings:

• No – List is visible in public catalogs (subject to other settings).
• Yes – List is hidden; only direct knowledge of the list name allows interaction.
• Service – Visibility is limited to the list's service area (e.g., same as Service= restrictions).

Common use: Hide internal, sensitive, or specialized lists (Yes or Service).

Purpose: Limits the number of messages a user can post to a list per day.

Typical value:

Daily-Threshold= 200

Meaning: A sender who exceeds this number of posts in a day will be blocked or queued, depending on configuration. Helps control spam or runaway scripts.

Purpose: Sets default subscriber options applied at subscription time to new users.

Typical values: A comma-separated list of SET options, for example:

Default-Options= DIGEST,NOREPRO
Default-Options= NOPOST
Default-Options= REVIEW,NOACK

Common option meanings:

• DIGEST – Deliver messages as periodic digests instead of individual emails.
• INDEX – Deliver message indices instead of full content.
• MAIL – Normal delivery of individual posts (default in many cases).
• NOMAIL – Do not deliver posts (useful for special accounts or sync targets).
• NOREPRO – Do not send the subscriber copies of their own posts.
• NOACK – No acknowledgment messages upon posting.
• REVIEW – Posts from this subscriber are moderated.
• NOPOST – Subscriber cannot post.

Common use: Set default behavior (digest vs. regular, moderation of new users, restricting posting) without having to manually adjust each new subscriber.

Purpose: Assigns one or more predefined topics to new subscribers by default, when the list uses topic-based subscriptions.

Typical value:

Default-Topics= Events,Announcements

Meaning: Upon subscription, new users are automatically subscribed to these topics unless they explicitly choose otherwise.

Common use: Multi-purpose lists where only some content (e.g., "Announcements") should be on by default, while others ("Chat", "Jobs", etc.) are opt-in.

Purpose: Controls generation of digest versions of the list.

Typical format:

Digest= Yes,Same,Daily,Size(2000)

Common parameters:

• Yes/No – Enable or disable digest generation.
• Same / Separate – Whether digest shares same template/address or separate.
• Frequency – Typically Daily.
• Size(n) – Size-based split; e.g., Size(2000) for approx 2,000 lines.

Common use: Provide a digest option for busy lists so users can receive fewer messages.

Purpose: Defines the editor(s) for the list, especially when Send= Editor or a moderated workflow is used.

Typical values:

Editor= editor1@example.com
Editor= jane@example.com,john@example.com

Notes:

• The first editor must be a real, reachable person.
• Editors receive posts that require approval and can accept/reject them.

Common use: Required for edited/curated lists and many moderated discussion lists.

Purpose: Specifies where error reports, bounces, and various system reports for this list are sent.

Typical values:

Errors-To= owner@example.com
Errors-To= list-errors@example.com

Common use: Direct bounces and error notices to a functional mailbox, a ticketing system address, or a dedicated "errors" address rather than individual owners when appropriate.

Purpose: Controls the list's use as a file distribution mechanism via FILESERV features.

Typical values:

Files= No
Files= Yes

Common use: Often disabled (No) for modern deployments where file distribution is handled by other systems (SharePoint, CMS, etc.).

Purpose: Sets the minimum number of columns used to display addresses in REVIEW output.

Typical value:

Indent= 40

Use: Mostly cosmetic; can be left at default in most environments.

Purpose: Sets the language used for system-generated messages (welcome messages, error messages, etc.) for this list.

Typical value:

Language= English

Meaning: Must correspond to a valid mail template set installed on the server (e.g., DEFAULT.MAILTPL for English or other language-specific templates).

Purpose: Limits the maximum number of subscribers for a list.

Typical value:

Limits= Sub(200)

Meaning: The list may not have more than 200 subscribers. Only the LISTSERV maintainer may change this setting.

Purpose: Defines a globally unique List-ID used in email headers to identify the list.

Typical value:

List-ID= mylist-l.dartmouth.edu

Meaning: Helps email clients and filtering systems recognize the list as a distinct identity; useful for modern mail routing and list recognition.

Purpose: Controls the distribution engine used by LISTSERV.

Typical value:

Mail-Via= DISTRIBUTE

Meaning: DISTRIBUTE is the modern efficient delivery engine used for scalable distribution. Other values are rarely used in current setups.

Purpose: A collection of advanced flags that change list behavior in specific ways.

Example:

Misc-Options= PROCESS_SPAM_FEEDBACK

Meaning: Instructs LISTSERV to process feedback loop spam complaints for the list, automatically removing complainers and updating changelogs.

Note: Many Misc-Options= settings are advanced; typically set by site administrators following product documentation.

Purpose: Defines who receives moderation requests when a list is configured for moderation (e.g., via the web moderation interface).

Typical values:

Moderator= All
Moderator= jane@example.com,john@example.com

Value meanings:

• All – All configured moderators receive moderation requests.
• List of addresses – Only these addresses receive moderation requests.

Common use: For lists where multiple people share moderation duties, especially high-volume lists.

Purpose: Used internally by LISTSERV when a new list is created, often to mark that the list is in an initial configuration state.

Use: Usually managed automatically; list owners rarely need to modify this directly.

Purpose: Used when LISTSERV is gating to a USENET newsgroup; defines the newsgroup name(s).

Use: Only relevant where a LISTSERV–USENET gateway is configured.

Purpose: Controls whether the list is archived and how archives are stored and accessed.

Typical format:

Notebook= Yes,D:\LISTSERV\LISTS\MYLIST,Monthly,Private
Notebook= Yes,/var/listserv/archives/MYLIST,Weekly,Public

Parameters (in order):

1. Yes/No – Enable or disable archiving.
2. Path – Filesystem path where archives are stored.
3. Frequency – Archive segmentation: Daily, Weekly, Monthly, etc.
4. Access – Public, Private, or similar; controls who can read archives.

Common use: Enable archives for most discussion lists. Use Private for internal or sensitive content.

Purpose: Controls whether owners receive notifications about subscription changes and other list events.

Typical values:

Notify= Yes
Notify= No

Common use: Turn Yes on for small, carefully managed lists; consider No for very large lists where subscription churn would flood owners with messages.

Purpose: Defines the list owner(s) who have full administrative control over the list.

Typical values:

• Single address: Owner= ty@example.com
• Multiple owners: Owner= admin1@example.com,admin2@example.com
• Quiet owner: Owner= Quiet:,jane.doe@example.com

Value meanings:

• Regular owner – Receives administrative notices, error messages, and can manage subscribers and list settings.
• Quiet: owner – Has the same privileges but does not receive routine administrative mail (used to reduce noise).

Common use: Every list must have at least one owner. Add Quiet owners for backup or escalation contacts without flooding their inbox.

Purpose: Defines a set of peer servers that share a distributed version of the list.

Meaning (simplified): LISTSERV can distribute subscribers across multiple servers to optimize delivery or keep traffic local to a region/domain.

Note: This is an advanced feature typically managed by the LISTSERV site administrator.

Purpose: Historically controlled when the list would be loaded/processed at LISTSERV startup.

Note: Rarely used in modern deployments; typically left unset.

Purpose: Defines a list-level password used for validating certain operations, particularly for peered lists.

Typical value:

PW= someRandomString

Important: Modern guidance generally prefers personal LISTSERV passwords instead of list passwords, except where peering requires a shared value.

Purpose: Forces subscribers to periodically confirm that they still want to be on the list.

Typical values:

Renewal= Yearly
Renewal= 6-Monthly,Delay(10)

Value meanings:

• Yearly, Monthly, 6-Monthly, etc. – Renewal interval.
• Delay(n) – How many days LISTSERV waits for the confirmation before removing the user (default 7 days if omitted).

Behavior: LISTSERV sends a renewal notice. If the subscriber does not confirm within the delay window, their subscription is automatically deleted.

Common use: Prevent lists from growing stale with inactive or abandoned addresses, especially large public lists.

Purpose: Controls where replies to list messages are directed.

Common values:

Reply-To= List
Reply-To= Sender
Reply-To= Sender,Respect
Reply-To= List,Respect

Value meanings (simplified):

• List – Replies go back to the list address by default.
• Sender – Replies go only to the individual sender of the message.
• Respect – Instructs LISTSERV to respect any existing Reply-To header from the original message; reduces header conflicts.

Common use:

• Sender – Avoids accidental "reply all" to large lists.
• List – Encourages shared discussion when that's the goal.
• Sender,Respect – Balanced approach that avoids overriding a carefully set Reply-To on the original message.

Purpose: Controls who can see the list of subscribers (via REVIEW commands or web UI).

Common values:

Review= Public
Review= Owner
Review= Private

Value meanings:

• Public – Anyone can view the subscriber list.
• Owner – Only owners can view the subscription list.
• Private – Even subscribers cannot view the membership; only owners and site managers can.

Common use: Use Owner or Private for privacy-sensitive lists (students, HR, sensitive communities).

Purpose: Historically used to enforce stricter behavior for some commands.

Note: In modern LISTSERV releases, other mechanisms (such as Validate= and configuration settings) are typically preferred.

Purpose: Controls who may post messages to the list.

Common values:

Send= Public
Send= Private
Send= Editor
Send= Owner

Value meanings:

• Public – Anyone (including non-subscribers) can post.
• Private – Only subscribers may post.
• Editor – Posts must go through the editor(s) for approval; typical for moderated lists.
• Owner – Only owners may post; often used for announcement-only lists.

Common use:

• Public – Open community lists.
• Private – Internal working groups.
• Editor – Newsletters, curated lists, moderated discussions.
• Owner – One-way announcement channels.

Purpose: Restricts which email addresses are allowed to subscribe, typically based on domain or host patterns.

Typical values:

Service= *
Service= *.dartmouth.edu
Service= *@alumni.dartmouth.edu

Value meanings:

• * – No restriction; any domain may subscribe.
• *.dartmouth.edu – Only email addresses at dartmouth.edu and its subdomains may subscribe.
• *@alumni.dartmouth.edu – Only addresses at that specific host/domain may subscribe.

Common use: Restrict lists to internal staff/faculty, students, or alumni by domain.

Purpose: Sets the maximum size of messages accepted by the list.

Typical value:

Sizelim= 500K

Meaning: Messages larger than this limit are rejected. Units typically in bytes with suffixes (K, M) depending on version/config.

Purpose: Controls what statistics are kept and who can see them.

Typical values (simplified):

Stats= None
Stats= Normal,Public
Stats= Normal,Private

Value meanings:

• None – No stats kept or displayed.
• Normal – Normal statistic collection (posting counts, membership, etc.).
• Public – Stats are visible to subscribers or general users.
• Private – Stats are restricted (owners/admins only).

Purpose: Automatically prepends a tag to the subject line of list messages.

Typical value:

Subject-Tag= [MYLIST]

Meaning: Messages from the list will have subjects like [MYLIST] Meeting on Friday, making them easier for subscribers to filter and recognize.

Purpose: Allows a list (the "super-list") to be composed partially or entirely of other lists (sub-lists).

Meaning: Messages posted to the super-list are distributed to subscribers of the sub-lists, enabling hierarchical list structures.

Common use: "Umbrella" lists that send announcements to multiple sub-audiences via their own lists.

Purpose: Defines topic "tags" or substreams that subscribers can opt in/out of within a single list.

Typical value (simplified):

Topics= Announcements,Events,Jobs

Meaning: Each topic can be used to mark posts; subscribers can choose which topics they receive.

Purpose: Controls translation of control characters appearing in list mail.

Use: Rarely changed; may be useful when dealing with legacy systems or problematic character sets.

Purpose: Determines what level of security/validation is required for commands affecting this list (add/delete, configuration changes, etc.).

Common values (simplified):

Validate= Yes
Validate= No
Validate= Yes,Confirm

Value meanings:

• Yes – LISTSERV requires appropriate credentials (e.g., password) for sensitive commands.
• No – Minimal validation (not recommended for most lists).
• Yes,Confirm – Commands must be validated and confirmed (e.g., OK reply) to execute.

Common use: Use Yes or stronger settings for almost all production lists to prevent unauthorized changes.