view man/mlmmj-receive.1 @ 919:e371a935a0cd default tip master

Added tag RELEASE_1_3_0 for changeset 570dd6d4942b
author Ben Schmidt
date Thu, 25 May 2017 09:08:47 +1000
parents 28f313a329ed
children
line wrap: on
line source

.TH mlmmj-receive "1" "September 2004" mlmmj-receive
.SH NAME
mlmmj-receive \- receive mails for an mlmmj managed mailinglist
.SH SYNOPSIS
.B mlmmj-receive
\fI\-L /path/to/listdir \fR[\fI\-h\fR] [\fI\-V\fR] [\fI\-P\fR] [\fI\-F\fR]
.HP
\fB\-h\fR: This help
.HP
\fB\-F\fR: Don't fork in the background (debugging only)
.HP
\fB\-L\fR: Full path to list directory
.HP
\fB\-P\fR: Don't execute mlmmj-process (debugging only)
.HP
\fB\-V\fR: Print version
.SH DESCRIPTION
The mlmmj-receive binary is the one specified in the mailserver configuration
file (aliases file), which writes the mail to the <listdir>/incoming directory
and invokes mlmmj-process unless the \fB\-P\fR option is specified. On systems
using mailservers supporting the \fB/etc/aliases\fR file, a line to activate
an mlmmj managed mailinglist would look like this:
.LP
list: "|/usr/bin/mlmmj-receive \-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 \fB\-F\fR 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.

.SH "SEE ALSO"
mlmmj-process(1)
.SH AUTHORS
This manual page was written by the following persons:
.HP
S\[/o]ren Boll Overgaard <boll@debian.org> (based on html2man output)
.HP
Mads Martin J\[/o]rgensen <mmj@mmj.dk>