mlmmj-recieve(1) [suse man page]

mlmmj-recieve(1)					      General Commands Manual						  mlmmj-recieve(1)

NAME

       mlmmj-recieve - recieve mails for an mlmmj managed mailinglist

SYNOPSIS

       mlmmj-recieve -L /path/to/listdir [-h] [-V] [-P] [-F]

       -h: This help

       -F: Don't fork in the background (debugging only)

       -L: Full path to list directory

       -P: Don't execute mlmmj-process (debugging only)

       -V: Print version

DESCRIPTION

       The  mlmmj-recieve  binary  is  the  one specified in the mailserver configuration file (aliases file), which writes the mail to the <list-
       dir>/incoming directory and invokes mlmmj-process unless  the  -P  option  is  specified.  On  systems  using  mailservers  supporting  the
       /etc/aliases file, a line to activate an mlmmj managed mailinglist would look like this:

       list: "|/usr/bin/mlmmj-recieve -L /var/spool/mlmmj/list/"

       It's very important to specify the full path to the binary, or the mailinglist will not function.

       When  the  -F  option is used, it will not fork in the background. The reason it forks is that if delivery of a mail takes longer time than
       the mail server will allow a command to be idle before presumed dead, the mail server would kill it.

SEE ALSO

       mlmmj-process(1)

AUTHORS

       This manual page was written by the following persons:

       Soren Boll Overgaard <boll@debian.org> (based on html2man output)

       Mads Martin Jorgensen <mmj@mmj.dk>

mlmmj-recieve							  September 2004						  mlmmj-recieve(1)

mlmmj-process(1)					      General Commands Manual						  mlmmj-process(1)

NAME

       mlmmj-process - process mail for an mlmmj managed mailinglist

SYNOPSIS

       mlmmj-process -L /path/to/list -m /path/to/mail [-h] [-P] [-V]

       -h: This help

       -L: Full path to list directory

       -m: Full path to mail file

       -P: Don't execute mlmmj-send (debugging only)

       -V: Print version

DESCRIPTION

       This is the binary which processes a mail. Examples of what such processing is:

       o   Access control

	   Using  the  access  rules  specified in <listdir>/control/access to perform access control to the list. This is done before headers are
	   stripped, so one can create allow rules based on headers that are later stripped.

       o   Header stripping

	   Headers specified in <listdir>/control/delheaders are deleted from the mail.

       o   Header addition

	   Headers specified in <listdir>/control/customheaders are added to the mail.	This could be headers like List-ID: or Reply-To:

       o   List control

	   In case there's a mail with a recipient delimiter it's not a regular list mail.  Processing of these happens in mlmmj-receive as  well.
	   Examples  of  such are subscription requests, mails to owner etc.  It will base it's recipient delimiter detection on the Delivered-To:
	   header if present. If not, the To: header is used.

       o   Moderation

	   If the list is moderated, it will happen in mlmmj-process.

       When processing is done, it will invoke the needed binary according to whatever mail it is. If it's a subscription request it  will  invoke
       mlmmj-sub, if it's a regular list mail it will invoke mlmmj-send.

SEE ALSO

       The file TUNABLES from the mlmmj source distribution or in the documentation directory of the operating system distribution.

AUTHORS

       This manual page was written by the following persons:

       Soren Boll Overgaard <boll@debian.org> (based on html2man output)

       Mads Martin Jorgensen <mmj@mmj.dk>

mlmmj-process							  September 2004						  mlmmj-process(1)