User Commands ezmlm-request(1) NNNNAAAAMMMMEEEE ezmlm-request - Process subject line and body ezmlm commands SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt [ -ffff _c_o_n_f_i_g ] _d_i_r DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt processes ezmlm commands in the subject line or message body. eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt enables these uses to send the message to _l_i_s_t-rrrreeeeqqqquuuueeeesssstttt@_h_o_s_t with the complete command address line in the subject field, or with commands and arguments separated by white space. eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt uses the text to construct a ezmlm command message to the list. If the subject does not start with a letter, eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt 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 ezmlm command address format or formatted as: ccccoooommmmmmmmaaaannnndddd[list@listhost[[[[uuuusssseeeerrrr@@@@uuuusssseeeerrrrhhhhoooosssstttt]]]]]]]] eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt when invoked with the -ffff switch and a confi- guration file (see below), ignores the subject and processes the first body line (per rules above) in conjunction with the configuration file. It also services the lllliiiissssttttssss and wwwwhhhhiiiicccchhhh commands. This can be used to construct a global list inter- face, similar to that used by some other mailing list managers. Messages at the _l_i_s_t-rrrreeeeqqqquuuueeeesssstttt@_h_o_s_t are restricted to the local list. When eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt is invoked with the -ffff _c_o_n_f_i_g switch, command messages are limited to lists in _c_o_n_f_i_g or at the local host. Invalid requests for an existing ezmlm list will lead to a ``help'' message from eeeezzzzmmmmllllmmmm----mmmmaaaannnnaaaaggggeeee((((1111)))). OOOOPPPPTTTTIIIIOOOONNNNSSSS -ffff _c_o_n_f_i_g Function as a global interface to ezmlm lists in accor- dance with _c_o_n_f_i_g. This file consists of lines start- ing in the first position with ``list@host:listdir:description''. Lines that are blank or start with ``#'' are ignored. ``listdir'' and ``descrip- tion'' are optional. If only ``list@host'' is given, the list is used to restrict commands (see below), but not listed. To allow the list to be shown by a ``list'' command, use ``list@host:''. To specify only the list name and description, use ``list@host::description''. SunOS 5.11 Last change: 1 User Commands ezmlm-request(1) If ``listdir'' is present, the wwwwhhhhiiiicccchhhh command attempts to determine if the user is a subscriber of the list. NNNNOOOOTTTTEEEE:::: this will work only if the user running eeeezzzzmmmmllllmmmm---- rrrreeeeqqqquuuueeeesssstttt has read access to the lists subscriber data- base. If ``listhost'' is not specified, eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt will use the ``listhost'' from the first _c_o_n_f_i_g entry match- ing ``listlocal''. If ``listhost'' is specified, but not found in _c_o_n_f_i_g, it is set to the contents of _d_i_r////oooouuuutttthhhhoooosssstttt. UUUUSSSSAAAAGGGGEEEE Place an invocation of eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt in _d_i_r////mmmmaaaannnnaaaaggggeeeerrrr anywhere before the eeeezzzzmmmmllllmmmm----mmmmaaaannnnaaaaggggeeee((((1111)))) line. Alternatively, set up _d_i_r////rrrreeeeqqqquuuueeeesssstttt with an invocation of eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt. Make a link from ~/._q_m_a_i_l-_l_i_s_t-_r_e_q_u_e_s_t to this file. For the global interface, place ////ppppaaaatttthhhh////eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt ----ffff _c_o_n_- _f_i_g _d_i_r into a file. Link ~/._q_m_a_i_l-_e_z_m_l_m and ~/._q_m_a_i_l- _e_z_m_l_m-_d_e_f_a_u_l_t to this file. The latter allows eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt to handle its own bounces as well as to reply to messages to e.g. ``user-ezmlm-lists@listhost''. Create _d_i_r////iiiinnnnllllooooccccaaaallll and _d_i_r////oooouuuuttttllllooooccccaaaallll with ``user-ezmlm'', _d_i_r////oooouuuutttthhhhoooosssstttt with ``listhost'', _d_i_r////hhhheeeeaaaaddddeeeerrrrrrrreeeemmmmoooovvvveeee with headers to be stripped (copy from a list), _d_i_r/_t_e_x_t////hhhheeeellllpppp, _d_i_r/_t_e_x_t////ttttoooopppp, and _d_i_r/_t_e_x_t////bbbboooottttttttoooommmm with the appropriate texts. Also, create _c_o_n_f_i_g with the appropriate contents. Mail to ``user-ezmlm@listhost'' will now be answered by eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt. RRRREEEECCCCOOOOGGGGNNNNIIIIZZZZEEEEDDDD CCCCOOOOMMMMMMMMAAAANNNNDDDDSSSS Any command not recognized by eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt is assumed to be valid, as long as it consists of only letters, numbers, hyphen, underscore, period, and ``+''. This allows eeeezzzzmmmmllllmmmm---- rrrreeeeqqqquuuueeeesssstttt to correctly handle commands added by the list owner. A number of commands are recognized by eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt but not processed. Instead they are mapped to hhhheeeellllpppp without argu- ments. These are: ssssyyyysssstttteeeemmmm, ppppuuuutttt, and sssseeeetttt. eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt also handles a number of aliases for ezmlm commands. Since eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt only passes on requests to the list, local restrictions apply. For commands that have aliases, accepted aliases are listed: ssssuuuubbbbssssccccrrrriiiibbbbeeee sub SunOS 5.11 Last change: 2 User Commands ezmlm-request(1) uuuunnnnssssuuuubbbbssssccccrrrriiiibbbbeeee unsub, signoff, remove. iiiinnnnddddeeeexxxx ind. lllliiiisssstttt recipients, showdist, review, rev, who. Some commands are handled differently when used without argu- ments: qqqquuuueeeerrrryyyy Treated like ``which''. lllliiiisssstttt Treated like ``lists''. BBBBUUUUGGGGSSSS eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt places stricter requirements on addresses than rfc822. Thus, some addresses that are rfc822-compliant can- not be used as eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt command arguments. If you fix this, please send a patch to lindberg@id.wustl.edu. I think qmail has the same restriction, though. eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt uses NUL as a line terminator internally. Thus, if will fail if NUL is found within the line it tries to interpret as a command. It is harmless, other than that the remainder of the line will be ignored. The eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt ``which'' command does not differentiate between a list for which the command is not available, a list for which the subscriber db is not accessible, and a list for which the address is not a subscriber. This should be considered a feature. BBBBUUUUGGGGSSSS eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt when used as a global interface and receiving multipart messages assumes that the first line of the fist part is the command. Further, it assumes that the first line starting``--'' is the first MIME boundary. This is virtually always true, but it is easy to construct legal messages that do not fit these assumptions. eeeezzzzmmmmllllmmmm----rrrreeeeqqqquuuueeeesssstttt in the global interface role will fail if this first part or the entire message is base64 encoded. SSSSEEEEEEEE AAAALLLLSSSSOOOO ezmlm-get(1), ezmlm-manage(1), ezmlm-send(1), ezmlm(5) SunOS 5.11 Last change: 3