Majordomo List Manager

From Webmin Documentation
Jump to: navigation, search
The module Majordomo List Manager is currently unmaintained.

Either the feature is obsolete, or the feature is updated such way that webmin no longer interfaces correctly.
Majordomo at wikipedia

This page documents the process of setting up mailing lists on your system using Webmin and the freely available Majordomo list management program.

Introduction to mailing lists and majordomo

Mailing lists provide a way of facilitating group discussions via email, or broadcasting messages to multiple email addresses. At its heart, a mailing list is simply an email address that forwards all mail sent to it to a list of member addresses. Typically, messages are modified so that replies go back to the list address instead of to the original sender, making it easy for members to participate in a group discussion via email.

Majordomo is the most popular mailing list management program for Linux and Unix systems. As well as forwarding mail from the list address to members, it handles subscription and un-subscription, moderation, and message filtering. It can append headers and footers to messages, send out periodic digests containing list mails from the past few days, create a archives of list messages and much more.

Because it is written in Perl, Majordomo will run on almost all versions of Unix, and behaves the same on all supported operating systems. It only requires that you have a mail server installed that can forward messages to a program or to a file of addresses, which Sendmail and Postfix can do. See chapter 37 for more information on setting up Sendmail on your system.

Users of a mailing list typically subscribe by sending email to the special Majordomo address on your system, such as Majordomo@example.com. In fact, there are several types of commands that can be send to this address by simply including them in a message body, such as lists, subscribe and unsubscribe.

For example, to add yourself to a mailing list you could just send email to Majordomo@example.com containing the line subscribe example-list yourname@example.com . A single message can contain several commands, one on each line. After Majordomo receives a message, it will process the commands and send back a response email containing information about the success or failure of each command and any information that they produce.

Of course, before any of these commands will work on your system you must set up Majordomo and create at least one mailing list. The following sections explain how.

The Majordomo List Manager module

This module allows you to set up and manage multiple Majordomo mailing lists on your system. It is designed to interface with the Sendmail Configuration module to set up the mail aliases that Majordomo needs to operate, but can be used with any mail server that uses an /etc/aliases file. If you are not using Sendmail, see the Using other mail servers section for details on how to configure the module to work with your server. If Webmin detects that Sendmail is not installed, an error message will be displayed on the main page notifying you that its configuration file cannot be found.

Like other email related modules, this one can be found under the Servers category in Webmin. When you enter it, the main page displays a table of icons, one for each mailing list on your system. The screenshot below shows an example.


The Majordomo module main page

For Majordomo to operate, it requires that the Majordomo and Majordomo-owner mail aliases be defined and forward messages to the Majordomo program and the list administrator respectively. If the module detects that these aliases do not exist (usually because you have never set up Majordomo or used the module before), a field labelled Owner email address will be displayed on the main page.

You must enter the address of the master mailing list administrator (usually yourself) into this field, and hit the Setup Aliases button next to it. The necessary aliases will be created, and the main page re-displayed without the button and field. Until you do this, Majordomo will not work properly - people will not be able to subscribe and unsubscribe, get information about existing mailing lists and so on.

Naturally, if the module cannot find Majordomo on your system at all, the main page will display an error message instead of any of the icons and fields mentioned above. If you are sure that it really is already installed, then read the *Configuring the Majordomo List Manager module* section for instructions on how to adjust the paths that the module uses to find the configuration files and programs.

Only a few operating systems and versions of Linux come with Majordomo as standard, such as OpenLinux, SuSE Linux, MSC.Linux, Debian Linux and AIX. If you are running one of these, check your operating system CD or website for the Majordomo package, and install it using the Software Packages module. Users of all other operating systems will need to download, compile and install the source code from http://www.greatcircle.com/majordomo/. The module assumes that you will use the package on systems that have one, and the source code if not. If you installed the source even though there was a package available, or used a package that I don't know about, you will need to adjust the paths on the Module Config page.

If you are already an extensive user of Majordomo, the module should find and display all your existing lists and their settings. However, it depends on the majordomo.cf not being too different from the original format, so that it can be parsed properly. If you have made extensive modifications to this file, the module may not find some or all of your lists.

Neither does it deal well with multiple virtual email domains. Some systems have one Majordomo configuration file for each domain, and possibly multiple alias files as well. The only way to use the module in this situation is to clone it once for each domain (as explain in chapter 51), and configure each clone to use a different majordomo.cf file.

Using other mail servers

By default, this module assumes that you are using the Sendmail Mail Server. However, many people prefer alternatives like Postfix Mail Server or QMail Mail Server due to their superior configuration file formats, reliability and design. Fortunately, the module can work with any mail server that uses an aliases file in the same format as Sendmail's /etc/aliases.

All that you need to do is tell the module where the aliases file is located, instead of having it read the Sendmail configuration and find it automatically. The steps to do this are:

  1. On the module's main page, click on the Module Config link. This will bring up the standard module configuration form.
  2. For the Sendmail-style aliases file field, de-select the Get from sendmail.cf option and enter the full path to your mail server's aliases file. This will usually be something like /etc/aliases or /etc/postfix/aliases.
  3. Click the Save button to return to the main page. Any error message about the Webmin's inability to find the sendmail.cf will have disappeared.
  4. Click on the Edit Majordomo Options button at the bottom of the page, and fill in the Sendmail command path field with the path to a program that works in the same way as the real sendmail command. All mail servers come with a program like this to preserve compatibility with programs that expect Sendmail to be installed, usually found at /usr/sbin/sendmail or /usr/lib/sendmail. Majordomo uses this command to send outgoing email to list members.
  5. Click Save to return to the main page. The module and Majordomo will now function properly with your mail server.

Not all mail servers have a standard aliases file, and so this module cannot be used with them. Qmail requires a patch before it will read an aliases file, as normally it uses .qmail files in the /var/qmail/aliases directory to define aliases.

Creating a mailing list

Once the Majordomo module has been set up correctly, you can use it to create a new mailing list. Every list must have a name that cannot be used by any other list, Unix user or email alias. Typically lists are named like example-list or engineering-l, but really any short name consisting of numbers, letters and dashes is allowed. The name forms the part of the list's email address before the @, so the resulting address will be something like example-list@example.com.

To create a list, the steps to follow are:

  1. On the module's main page, click on the Add a new mailing list link above or below the table of existing list icons. This will bring you to the list creation form, shown in the screenshot below.
  2. Enter the chosen name into to List name field.
  3. Fill in the List maintainer's address field with the email address of the person who will be responsible for this list. They will receive notifications of subscriptions and un-subscriptions, and bounce messages if delivery to a list member fails.
  4. The password entered in the Maintenance password field can be used by the maintainer to change the list's configuration by email. Make sure that this password does not fall into the hands of anyone else, as it grants full control over the list to anyone who knows it. Typically, you will not need to configure the list via email anyway, as this Webmin module provides a much nicer interface than manually editing the configuration file.
  5. In the Description field, enter a short description of this list that will be displayed next to its name when a user sends the lists command to Majordomo.
  6. The text in the Introductory message field will be sent to all new list members when they subscribe. You should enter a description of the list, posting guidelines and any other information that new subscribers might need to know.
  7. To have a footer appended to each email sent to the list, fill in the Forwarded mail footer field. Often the footer contains the list name and information about how to un-subscribe.
  8. If you want this list to be moderated, change the *Moderated list?* field to Yes. A moderated list is one that required all messages sent to it be approved before they are sent to list members.
  9. If the moderator is the same as the list administrator, leave the Moderator's address field set to Same as maintainer. Otherwise, enter an email address into the adjacent text field- this address will receive a copy of every email sent to be list for approval.
  10. If you want Majordomo to store copied of messages sent to this list in archive files, select one of the options other than No from the Archive mailing list? menu. An archive is a collection of files under the list's directory that contains email to the list for a year, month or day.
  11. Finally, click the Create button to have the module create the list and all the Sendmail aliases that it needs to operate. You will be returned to the main page, which should now contain an icon for your new list.


Creating a new mailing list

People can subscribe to the new list and send email to it as soon as it is created. However, you will probably want to customize its settings some more before announcing its existence - the next few sections explain now.

Managing list members

Even though people can subscribed and un-subscribe themselves to and from a mailing list, you can also use this Webmin module to manage the membership list. To directly edit the member list, the steps to follow are:

  1. On the module's main page, click on the icon for the mailing list. This will bring you to a page which contains icons for various categories of list options.
  2. Click on the List Members icon to go to the membership management page shown in the screenshot below.
  3. On the page that appears, add to, remove from or edit the list of members in the text box. Any new subscribers that you add by editing this list will not receive a welcome email or confirmation message.
  4. Hit the Save button to make the new member list active.
    Managing mailing list members

The same page can also be used to subscribe people to the list. Just enter an address into the Subscribe address to list field and click the Add button. When a member is added this way, he will receive the usual welcome message as though he subscribed normally by sending email to Majordomo@yourdomain.com. Internally, the module does the subscription in the proper way by faking an email to Majordomo, instead of just directly updating the file containing list members.

An address can be deleted from the list by entering it into the Remove address from list field and hitting Remove. As far as the subscriber is concerned, there is no different between this method and just deleting his address from the member text box. Internally though the un-subscription is done by a faked email to Majordomo which tells it to delete the address from the member file, rather than Webmin updating that file directly itself.

Editing list information, headers and footers

After a list has been created, you can still edit the description, welcome message and footer that were chosen on the creation form. The steps to follow are:

  1. On the module's main page, click on the icon for the list.
  2. Click on the Messages and Description icon to bring up a page for editing the description, welcome and information message.
  3. To change the description shown in response to the lists command sent to the Majordomo address by users, edit the List description field.
  4. The Informative message field contains text that will be sent back in response to the info listname command, and possibly also to new subscribers. Change it to whatever you want.
  5. The welcome message is usually the same as the informative message. To change this, select As entered below for the Introductory message field and fill in the text box with a message to be sent to new subscribers.
  6. Click Save to return to the list icons page, and then hit the Headers and Footers icon.
  7. To have a header added to the top of all list messages, fill in the Resent email header field. Most lists don't use a header though - a footer is less annoying to readers.
  8. To edit the footer appended to the bottom of list messages, change the Resent email footer field.
  9. If you want every list message to have additional mail headers added to it, fill in the Extra SMTP headers for resent mail field. These must be in the standard email header format, such as: Subject: blah X-Mailing-List: example-list@example.com New headers cannot override those in forwarded messages, only add to them. If you want to change the subject or reply-to address, see the Editing forwarded email options section.
  10. Click the Save button at the bottom of the form. All the new list information, header and footer setting will be immediately active.

Editing subscription options

By default, Majordomo allows anyone to subscribe themselves to a newly created list, and sends a confirmation message to new members to make sure that they really do want to subscribe. These features prevent people from being subscribed against their wishes by someone else, but can be annoying on a small company mailing list with trusted users.

To change these and other subscription options, the steps to follow are:

  1. Click on the list's icon on the module's main page, and then on Subscription and Moderation.
  2. The Subscribe policy field controls who can be subscribed to the list. The options are: Anyone can subscribe themselves When selected, an address can only be added to the list (by an email to Majordomo) if the address that it comes from is the same. This security feature can be trivially defeated by faking the source address of a message though, and can be irritating to people who want to use a special address for subscriptions. Anyone can subscribe anyone When this option is selected, any address added to the list will be accepted. Maintainer approval required This option tells Majordomo to forward all subscription requests to the list maintainer for approval. It should be used if you want to control who can join the list, instead of allowing just anyone to sign up.
  3. Similarly, the Unsubscribe policy field controls who can be removed from the list. Its options are the same as the Subscribe policy field.
  4. To have Majordomo send a message to new addresses confirming their subscriptions, set the Require subscribe confirmation? field to Yes. This confirmation message must be replied to before the address is actually added to the list, indicating that the person really does want to subscribe. I would recommend always turning this feature on unless you are running a very small internal mailing list.
  5. If you want the welcome message (entered when the list was created) to be sent to all new members, set the Sent introductory message? field to Yes.
  6. The Add only raw addresses to list? field determines whether Majordomo stored complete addresses (like _Jamie Cameron <jcameron@webmin.com>_) or just raw addresses (like jcameron@webmin.com) in the membership list. Unless you want to be able to see the real names associated with subscriber addresses, this field should be set to Yes.
  7. If you want to list maintainer to receive a copy of all subscription and un-subscription requests, set the Forward subscribe/unsubscribe requests to maintainer? field to Yes. This does not mean that the maintainer must approve the requests though.
  8. The password specified in the Maintenance password field must be included in all messages to approve subscriptions or change the list's configuration by email. It should be give only to the maintainer, as anyone who knows it can edit any of the list's settings.
  9. To require every message to the list be approved by a moderator, change the Moderated list? field to Yes.
  10. The Moderator's address field controls where requests to approve messages to the list are sent to. You can either set it to Maintainer (in which case the address in the *Approval email address* field will be used), or enter something different.
  11. The Moderation password field is for entering a password that must be included in all messages that approve postings to the list. It should be known only by the moderator (if there is one) and yourself, otherwise subscribers could approve their own postings!
  12. To change the address of the list owner (to which email to _listname_-owner is sent), edit the Owner's email address field. The owner will receive bounce messages that are sent back if email to a subscriber cannot be delivered.
  13. To change the maintainer's address, edit the *Approval email address* field. All notifications of and requests for subscription and un-subscription will be sent to this person.
  14. Finally, click Save - the new settings will take effect immediately.

When confirmation is enabled for a list, anyone who sends a subscribe command to the Majordomo address will receive an email asking them to send back special auth command. This additional step guarantees that the person being added to the list actually wants to join, because the auth command contains a random number that Majordomo associates with the subscribing address.

When moderation or subscribe/unsubscribe approval is enabled, additional messages will be sent to the moderator's or maintainer's addresses. See the Moderating and maintaining a list section below for more information on how to actually deal with these emails.

Editing forwarded email options

When an email message is sent to the list, Majordomo does not just forward it to subscribers unchanged. Instead, it modifies the headers and possibly the content based on the list's configuration. The most common modification is the addition of a Reply-To header so that member replies will go to the list rather than to the original sender. In a group discussion list, this is generally what you want.

Other modifications that Majordomo can perform on list messages include adding some text to the subject line, and changing the priority. To configure them, the steps to follow are:

  1. On the module's main page, click on the list icon and then on Email Options.
  2. To have Reply-To header added to list email, enter the list's email address (such as _example-list@example.co_m) into the Reply-To: address in resent email field. Selecting the None option will cause reader replies to go the original sender of each message by default.
  3. To set the sender address of forwarded messages, fill in the Sender: address in email field. This should be owner-_listname_, which is forwarded to the actual owner's address. Any bounce messages that come back from subscribers will be send to this address.
  4. The Hostname for resent email should be set to the mail domain of your system, such as example.com. Leaving the Default option selected tells Majordomo to work out the domain automatically, which it may not do correctly.
  5. To have some text prepended to the subject line of every list message, enter it into the Subject: prefix for resent email field. Typically the list name in brackets will be added, such as [example-list].
  6. To change the priority of list messages, select one from the Resent email priority menu. Traditionally mailing lists use the Bulk priority, and some programs depend on this to identify list email.
  7. Every email message has several Received headers, each of which is added by a mail server that the message passes though. To have Majordomo strip them from forwarded messages, change the Remove Received: headers from resent email field to Yes. You may want to do this to hide the IP address and other details of people who post to the list.
  8. To limit the size of messages that can be sent to the list, fill in the Maximum allowable message size field. On a list with many members, it is wise to stop people sending large messages due to the load that their forwarding will place on your system and network. A 40,000 byte limit is quite enough for the kinds of text emails that most people send to a mailing list.
  9. When you are done editing email forwarding options, click Save. As long as there are no errors in the form, you will be returned to the list option icons page.

Even though the addition of a Reply-To header is convenient for most users, some people consider it to be a bad idea. Because almost all email clients have a reply to all button for sending email to the original sender and all recipients, there is no need for the normal reply button to send mail to the list. In fact, having a Reply-To header makes it difficult for readers reply to just the original sender instead of to the entire list.

Editing list access control

Majordomo can be configured to restrict who can get information about a list, who can post to it and the contents of messages that they send. Often you will want to restrict posting to list members or to a limited group of people, instead of allowing anyone in the world who knows the list address to send email to its members. However, these poster restrictions are not totally effective, as it is easy for anyone to forge their From address.

The steps to control access to a list are:

  1. On the module's main page, click on the list's icon to bring up the page of option category icons.
  2. Click on Access Control to display a form for editing information and posting restrictions.
  3. The first six fields on the page can be used to restrict access to the get, index, info, intro, which and who Majordomo commands (explained in the introduction). You may want to do this to hide details of the list from some or all people- in particular, the list of members should not be available to potential attackers. The fields, named Access to get command and so on, have the following options: Anyone The command is available to anyone who can send email to the Majordomo address. List members The command is only available to list members, identified by the From address of messages to Majordomo. Nobody Nobody can use the command for this list at all.
  4. The Majordomo command lists usually returns information about all mailing lists on your system. However, the field Include this list in response to lists command for can be used to limit the senders who will see this particular list, which can be useful if you want to hide it from casual queries. The available choices are: Everyone The list is visible to anyone who can send email to Majordomo. Addresses matching regexps Only senders whose addresses match one of the Perl regular expressions entered into the adjacent text box will be able to see the list. Addresses not matching regexps Only senders whose addresses do not match on the of entered regular expressions will be able to see this list.
  5. To limit posting to list members only, change the Who can post to the list? field to List members. This makes a lot of sense, as it protects your list from spammers who have somehow obtained its address. If only a few people should be allowed to post, create a file containing their email addresses and enter the path into the Addresses in file field. This option is useful for announcement lists on which most subscribers only receive information and cannot post.
  6. To block postings containing certain words or text, use the Taboo body regexps field. All banned words or sentences must be entered one per line with a / at the start and end, such as /smeg/.
  7. It is also possible to block messages whose headers match certain regular expressions, by filling in the Taboo header regexps field. For example, you could enter /Subject:.*money.*/ to block all postings with the word money in their subject line.
  8. When you are done on this page, click the Save button. The new restrictions will take effect immediately.

Moderating and maintaining a mailing list

In this command, password must be the maintenance password set for the list on the Subscription and Moderation page, list must be the name of the list to add the subscriber to, and address must be his email address. In fact, it is possible to use this command at any time to add someone to a list, even if they have not asked to join.

If you are the moderator for a mailing list, you will receive a message with a subject like BOUNCE: foo@bar.com: Approval required whenever someone tries to post to the list. In the body of the message will be the original email that was sent to the list address, which you are supposed to read to make sure it is appropriate for posting.

Unfortunately, the only way to approve a message is to save the entire email to a file and run the approve command on it. For example, if the message was saved to /tmp/email you would run _approve /tmp/email_ to send it to the list. In addition, you must create a file called .majordomo in your Unix home directory that contains the names of lists, their moderator passwords and Majordomo email addresses. The .majordomo file must be formatted like this: first-listname first-password Majordomo@whatever.com second-listname second-password Majordomo@example.com

Future versions of Webmin will hopefully simplify the approval process.

Deleting a mailing list

If a list is no longer needed, you can easily delete it and all associated files and aliases using this module. The membership list, configuration files and any archives will be permanently removed. The steps to delete a list are:

  1. On the module's main page, click on the list's icon.
  2. Hit the Delete List button below the table of option category icons. A confirmation page will be displayed, showing all the files and Sendmail aliases that Webmin will delete when removing the list. Because the aliases include any that start or end with the list name, make sure that none of your own unrelated aliases are included.
  3. To go ahead, click on the Delete List button. Once the deletion is complete, you will be returned to the main page of the module.

Creating a digest list

A digest mailing list is one that combines several messages from another list into a single email before sending it to subscribers. Digests are always associated with normal lists, and have their own subscribers who only receive postings in digest format. Digests are never moderated, and are not posted to by subscribers - instead, posts should go to the original list.

The number of messages that are combined into a single digest email can be determined by their size, or by a time period. Majordomo can be configured to send out a new digest once it reaches a certain size, or after a certain number of days from the time the first message was added. However, it will never send out an empty email to digest subscribers.

The process of adding a digest list is similar to that for adding a normal list, as explained in the Creating a mailing list section. The steps to follow are:

  1. On the module's main page, click on the Add a new digest list link. This will take you to the list creation form, which is similar to the one shown in the second screenshot above.
  2. Enter a name for the list into the List name field, such as example-digest. Traditionally a digest list will have the same name as the original list, but with -digest appended.
  3. Select the name of the original list that you want to send out in digest form from the Make digest of list menu. Although it is possible to have a digest of a digest, in practice this is not very useful.
  4. Enter the address of the person who is responsible for this list into the List maintainer's address field.
  5. Enter a password for the maintainer to use into the Maintenance password field. # In the Description field, enter a short description of this digest that will be displayed next to its name when a user sends the lists command to Majordomo.
  6. Fill in the Introductory message field with a message that will be sent to all new list members when they subscribe.
  7. To have a footer appended to each digest sent out, fill in the Digest mail footer field.
  8. To have the digest sent on a regular schedule, select Oldest message is for the Send digest when field and enter the number of days between digests into the adjacent field. This assumes that messages are being regularly posted to the list - because Majordomo only checks the age of the digest when a message is added, it is possible for the interval to be greater than the specified number of days in practice. Alternately, the have a digest email sent out when it reaches a certain size, select the Messages total option and enter the minimum number of lines that the digest must reach into the adjacent field. As soon as it exceeds this limit, the digest will be sent to subscribers.
  9. Finally, click Create to have Webmin create the new digest list and all the Sendmail aliases that it needs. The alias for the original list will be updated to support the digest as well.

Once a digest list has been added, an icon for it will appear on the main page. Just as with a normal list, you can click on it and then on the category icons to edit the membership list and change settings such as the subscription policy, footers, Reply-To address and so on. Typically the Reply-To address should be set so that replies to a digest email go to the original mailing list - in fact, there is no way to post directly to a digest list created by Webmin. Any mail to example-digest@example.com will bounce, because the module does not create a mail alias with that name.

Editing digest options

After a digest list has been created, you can still edit options that are specific to digests such as the time period or message size that will trigger an email. To do this, the steps to follow are:

  1. On the module's main page, click on the icon for your digest list, then on the Digest Options icon.
  2. To change the subject line used for digest messages, edit the Digest title field. By default, this will be set to whatever was supplied for the Description on the creation form.
  3. To have the digest sent out on a regular basis, enter a number of days for the Oldest message age before sending field. If the Unlimited option is selected, Majordomo will not take the age into account when deciding when to send.
  4. To have the digest sent when it reaches a certain size, enter the minimum number of lines into the Max digest size before sending field. Selecting Unlimited tells Majordomo to ignore the size when deciding when to send the digest. It is actually possible to enter values for both the Oldest message age and Max digest size fields. If so, it will be sent as soon as either condition is met. Alternatively, you can set both fields to Unlimited - however, this means that the digest will never be sent!
  5. Every digest message has volume and issue numbers which are included in the subject line. The current volume is shown in the Current volume number field - if you like, you can increase it by one every year, and re-set the issue number to 1 at the same time.
  6. The number set in the Current issue number field is automatically incremented by Majordomo every time a digest is sent out. You should only change this when changing the volume number.
  7. Click the Save button at the bottom of the page when you are done editing digest options. Any new settings will take effect immediately.

Editing global Majordomo options

There are a few options related to the email domain and mail program that effect all mailing lists, as well as the master Majordomo email address. Generally you will not need to adjust them, but if you do the steps to follow are:

  1. On the module's main page, click on the Edit Majordomo Options button to bring up the global options form.
  2. The Mail server hostname field must contain the default email domain name for your server, such as example.com. This can be overridden on a per-list basis by the Hostname for resent email field on the Email Options page, but it is simpler to set it globally here. The value entered here sets the Majordomo variable $whereami, which can be used in the subsequent fields.
  3. To change the address that Majordomo commands must be sent to, edit the Majordomo master address field. Changing this is rarely necessary though, and you must update the actual Majordomo email alias as well for it to work properly.
  4. To change the address of the Majordomo administrator, edit the Majordomo owner's address field. Typically this is set to an alias that forwards mail to the real owner address, which can be changed instead of this field.
  5. To have Majordomo use a different program for sending email, edit the Sendmail command path field. Whatever you enter must be able to able to accept the same parameters as the sendmail command - however, most replacements for this command supplied with other mail server packages will work.
  6. Click the Save button to make the new settings active.

Module access control

As WebminUsers explains, it is possible to give a Webmin user limited access to a module. People who are granted access to this module can be restricted to managing only certain mailing lists and prevented from creating new ones or editing global Majordomo options. This allows you to give a user the rights to edit his own lists, without giving him root access or control over other mailing lists.

Once a user has been given access to the module, to restrict him like this the steps to follow are:

  1. In the Webmin Users module, click on Majordomo List Manager next to the user's name. This will take you to the module access control form.
  2. Change the Can edit module configuration? field to No, so that he cannot edit the paths to Majordomo commands.
  3. In the Mailing lists this user can manage field, choose the Selected option and select the lists that he should be able to configure from the box below it. Or to let him manage all mailing lists, choose All lists.
  4. Change the Can edit global options? and *Can create new mailing lists?* fields to No.
  5. If the Can edit list membership? field is set to No, the user will be not be allowed to directly edit the member list or subscribe and un-subscribe people from within Webmin. From a security point of view, this doesn't really achieve much as the user will still be able to subscribe anyone he wants by sending mail to the Majordomo address with the list password.
  6. Click Save to make the restrictions active.

Configuring the Majordomo List Manager module

The configurable options for the Majordomo module are divided into two groups - those that control the module's operation and user interface which can be safely edited, and those related to configuration file and program paths. When the click on the Module Config link on the main page, the first groups of options are displayed under Configurable options, and the second under System configuration.

Fields in the latter group generally do not need to be changed unless you are not using the standard Majordomo package for your operating system, or if you are running a mail server other than Sendmail.