A remote administrator, in this case (#15), is an address that can add/remove addresses from the subscriber list.
To subscribe john@blah.com to the list mailinglist@domain.com, send mail to mailinglist-subscribe-john=blah.com@domain.com. Normally, john@blah.com will be asked to confirm(If (#7) is set). However, if you are a remote administrator, you will receive the confirmation request. Thus, john@blah.com does not need to participate. When you've successfully added the address, john@blah.com will receive a message acknowledging his subscription.
You can unsubscribe addresses (-unsubscribe) in the same manner. To unsubscribe john@blah.com to the list mailinglist@domain.com, send mail to mailinglist-unsubscribe-john=blah.com@domain.com. Normally, john@blah.com will be asked to confirm. However, if you are a remote administrator, you will receive the confirmation request(if (#9) is set). Thus, john@blah.com does not need to participate.
If the list is set up for subscription moderation, the list owner has to approve the user's subscription request. The process starts with a user's subscribe request, followed by the normal user confirmation (If required). After this, the list sends a second confirmation request to the list owner. If the list owner replies to this request, the user is accepted as a subscriber.
Users may unsubscribe at any time without owner assistance.
This refers to (#18). The features below require (#15) to be on.
A list of this type denies users not on the subscribers list from sending messages to the list.
On lists that do not have subscription moderation, users can add themselves to the "allow" database in the same way. Therefore allowing submission of material to the list from other addresses.
Archive access may also be restricted to subscribers. Depending on (#6). Like subscribers of the list or the digest list, addresses in the "allow" database are allowed to access the archive.
Just as you may want to allow some non-subscriber addresses to send messages to the list, you may want to (temporarily) prevent an address from posting to the list. This is easily defeated, but very useful if some defective mail robot or other mailing list sends messages to the list address. The system works just like the "allow" list, but is called "deny". To prevent john@blah.com from posting to mailinglist@domain.com, send mail to mailinglist-deny-subscribe-john=blah.com@domain.com and reply to the confirmation request, respectively.
You can do this only if you are a remote administrator and the list is set up to support this option (#15). Normal users cannot access the "deny" database. This database does not affect archive access.
This refers to #10 in the setup.
The list may be configured to allow remote administrators to obtain a list of subscriber addresses. If mailinglist@domain.com is set up with this option and you are a remote administrator, mail to mailinglist-list@domain.com will get you the list. If you are sending from another account, you can use mailinglist-remote=admin.net@domain.com to get the list to remote@admin.net. Of course, this will work only if remote@admin.net is a remote administrator.
Subscriber lists for the "digest", "deny" and "allow" databases are obtained in a similar manner by a message to mailinglist-digest-list@domain.com, mailinglist-deny-list@domain.com, or mailinglist-allow-list@domain.com.
Subscription log
For each subscription, the subscribers "From:" line is logged. Remote administrators can list this log by sending a message to maillist-log@domain.com or search it for specific entries with the maillist-log.abc@domain.com command, where "abc" are letters or numbers to be matched exactly, or an underscore ("_") to match any character.
A "moderator" is an address to which messages are sent for approval. The message will be passed on only if a moderator has approved it. The list acts on the first moderator reply it receives to accept or reject the post. Subsequent replies do not have any effect.
The lists may be set up with message moderation(#1). When the list receives a message, it saves it, sends a moderation request with the message enclosed to the moderator(s). The subject of moderation request is "MODERATE for ...".
If you would like to approve the message, just reply to the "Reply-To:" address of the moderation request. Usually, this is the default for the "reply" function of your mail program. Alternatively, click on the "accept" address or copy and paste it into the "To:" field of a new message.
To reject the message, reply to the "From:" address, click on the "reject" address, or copy and paste the "reject" address into the "To:" field of a new message. You can also just replace the text "accept" in the accept address with "reject". Optionally, type a comment between two lines starting with "%%%". The sender of the message will receive a message from the list explaining that the message was rejected. If you typed a comment, it will be put into the rejection notice.
The third alternative is to ignore the request. If no moderator has replied within 5 days, the message is returned to the sender with an explanation.
To minimize mail to busy moderators, the list does not confirm moderator actions. More than one moderator may reply. The message will not be duplicated. The first valid reply that is received will decide the fate of the message. The list will send an error message only if a later reply requests an action different from the one already taken. Thus, if you decide to accept the message, but another moderator has already rejected it, the list will notify you. If instead the message had been previously accepted, the list would log your request, but it will not send you a notification.
If a message is sent by a moderator, it is sent for approval to that moderator only. The approval is necessary since anyone can claim to be a moderator, but only the moderator will be able to receive the moderation request. This feature is very useful for announcement lists where any moderator can make an announcement without bothering the others, while at the same time non-moderators cannot post without permission.
In all transactions the list keeps the moderators' addresses secret, even from other moderators. If you want to tell the user who you are, send them a separate E-mail. Of course, a list owner may choose to make the moderators' identities public. The list also keeps subscriber addresses secret. Only if configured (#10) will it allow the addresses to be listed, and then only to remote administrators.
While remote administration (#15) and subscription moderation (#16) are enabled separately, the addresses are always the same. Message moderators can be a different group of addresses(done in the mail control panel after the list is setup), but in practice most lists use the same addresses for all 3 functions.
If configured, remote administrators may edit (via E-mail) the list's text files, such as the one sent in reply to the maillist-help@domain.com address. A list of editable files, their use, and instructions for editing may be obtained with the -edit command. Thus, for the list mailinglist@domain.com, send a message to mailinglist-edit@domain.com and follow the instructions.
Make sure that the list has remote editing #11, remote administration #15, and the trailer #17
enabled.
Second, send a message to listname-edit.trailer@domain.com where "listname" is
the name of your list and "domain.com" is your domain name. You will receive an email back from the ezmlm program which contains a lot of information and you should read all of this.
You'll find that there are two important things in this email, that pertain to editing the actual trailer.
The first is an address that will be of the look something like:
listname-ed.1044405305.trailer.nnicleoklagnadanipkf@domain.com
(this is just an example, you will receive a significantly different version of it though)
Reply to this email address, and edit the code that is contained in the following lines:
%%% START OF TEXT FILE
---------------------------------------------------------------------
To unsubscribe, e-mail: listname-unsubscribe@domain.com
For additional commands, e-mail: domain.com-help@domain.com
%%% END OF TEXT FILE
It is important that you don't edit the lines that start with '%%%%' whatsoever. Any changes to these lines will cause your edit to fail. Change the text in between them and send the message to the address included in the message( some email clients will allow you to simply reply to the message, but to be sure, you should copy the address from the email and paste it into the To: address of the message)
The list can process commands in the subject line or message body. Send a message to maillist-request@domain.com with the complete command address line in the subject field, or with commands and arguments separated by white space. If the subject does not start with a letter, it instead uses the first body line that starts with a letter. Processing terminates if a line with a hyphen in the first position is encountered. All commands are expected to be in the list command address format or formatted as:
command[maillist@domain.com[john@blah.com]]
For more specific information, see ezmlm.org's website, listed below.
Portions of this page are taken directly from the ezmlm faq, located at http://www.ezmlm.org
If you have any further questions or problems, please contact us at: support@fasturl.net