Next: , Previous: User's Introduction, Up: User's Manual


1.2 Sending commands to an ezmlm/idx mailing list.

ezmlm has a different address for each command. In essence, the address is the list name and the command. This is straight forward to interpret and therefore very fast. It also makes it very easy to send commands from the command line without having to worry about the subject and the message body (which are ignored).

Messages to the list address itself are sent to all subscribers and should never be used for administrative requests. If you have forgotten everything, send a message to ‘mailinglist-help@example.org’ for the list ‘mailinglist@example.org’. If the instructions returned do not help you solve the problem, send a message to ‘mailinglist-owner@example.org’ for human help, forwarding a message from the list and including any relevant information.

If you want to interact administratively with the ezmlm mailing list ‘mailinglist@example.org’, send an empty message (contents and subject are ignored) to ‘mailinglist-command@example.org’, replacing ‘command’ with the desired command. For some commands, you can add arguments. Here are a few examples, which will be discussed further below:

mailinglist-subscribe@example.org
Subscribe me. ezmlm will send you a confirmation request, and once you reply to it a message confirming that you are a subscriber.
mailinglist-subscribe-user=gol.com@example.org
Subscribe ‘user@gol.com’. Here the default subscriber address (the one you send from) is overridden by an argument to the -subscribe command. To subscribe any address of type ‘user.name@host.dom’ just replace the ‘@’ in the address with ‘=’ and add it after a hyphen to the command. In this case ‘mailinglist-subscribe-user.name=host.dom@example.org’. Of course, ezmlm will ask ‘user.name@host.dom’ to confirm the request.
mailinglist-unsubscribe@example.org
Unsubscribe me. ezmlm will send a confirmation request to your address and remove the address once you reply.
mailinglist-unsubscribe-user=gol.com@example.org
Unsubscribe ‘user@gol.com’.
mailinglist-query@example.org’(*)
Tell me if my address is subscribed to the list or not.
mailinglist-get.123@example.org
Get message 123 from the archive. If you specify a number that is larger than the highest message number in the archive, you'll receive the latest message.
mailinglist-get@example.org’(*)
Get the latest 30 messages from the archive. If the list has a digest, the messages returned are the messages received since the latest digest (the last message of the latest digest is returned so that there always will be at least one message).
mailinglist-get.45_67@example.org’(*)
Get messages 45-67 from the archive. No more than 100 messages can be returned per request. If the first argument is larger than the highest message number in the archive, you'll instead receive the latest 30 or so messages from the archive. For a list with a digest, you'll get the messages that have arrived since the last digest as well as the last up to 30 messages of that digest.
mailinglist-index@example.org’(*)
Send subject and author name for the last 100-200 messages. No more than 2000 entries are returned per request.
mailinglist-index.300_399@example.org’(*)
Send subject and author of messages 300-399.
mailinglist-thread.45@example.org’(*)
Receive an ordered set of all messages that have the same subject as message 45. ‘Re:’, etc, do not make a difference, so the returned set is the usually entire thread.
mailinglist-info@example.org’(*)
Send me some information about this list (the list owner decides how this command is supported).
mailinglist-faq@example.org’(*)
Send me the list of frequently-asked questions (and answers) for this list (the list owner decides how this command is supported).
mailinglist-digest-subscribe@example.org’(*)
You guessed it - subscribe to the digest list for ‘mailinglist@example.org’, provided there is one. Digest are usually sent about every other day, but this also depends on the message volume and settings adjusted by the list owner.
mailinglist-digest-unsubscribe@example.org’(*)
Yes, it's that easy!