diff options
| -rw-r--r-- | doc/mailman-install.tex | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/doc/mailman-install.tex b/doc/mailman-install.tex index 4cf96322..cc58115f 100644 --- a/doc/mailman-install.tex +++ b/doc/mailman-install.tex @@ -1053,7 +1053,7 @@ Norbert Bollow (NB). \longprogramopt{with-mail-gid} \program{configure} option. \emph{BN:} it highly depends on your mail storing policy. For example - if you use the simple \file{~alias/.qmail-*} files, you can use + if you use the simple \file{\~{}alias/.qmail-*} files, you can use \program{`id -g alias`}. But if you use \file{/var/qmail/users}, the specified mail gid can be used. @@ -1061,16 +1061,16 @@ Norbert Bollow (NB). \code{mailman} user (using ``virtualdomains'' on a list-only domain, for example), you will have to use \longprogramopt{with-mail-gid}=\var{gid of mailman user's group}. This is incompatible with having list aliases - in \file{~alias}, unless that alias simply forwards to + in \file{\~{}alias}, unless that alias simply forwards to \code{mailman-listname*}. \item If there is a user \code{mailman} on your system, the alias - \code{mailman-owner} will work only in \file{~mailman}. You have to do - a \program{touch .qmail-owner} in \file{~mailman} directory to create + \code{mailman-owner} will work only in \file{\~{}mailman}. You have to do + a \program{touch .qmail-owner} in \file{\~{}mailman} directory to create this alias. \emph{NB:} An alternative, IMHO better solution is to \program{chown - root ~mailman}, that will stop qmail from considering \code{mailman} to + root \~{}mailman}, that will stop qmail from considering \code{mailman} to be a user to whom mail can be delivered. (See ``man 8 qmail-getpw''.) \item In a related issue, if you have any users with the same name as one of @@ -1092,10 +1092,10 @@ Norbert Bollow (NB). \code{mailman} user in charge of this virtual domain. \item \emph{BN:}If inbound messages are delivered by another user than - \code{mailman}, it's necessary to allow it to access \file{~mailman}. - Be sure that \file{~mailman} has group writing access and setgid bit is + \code{mailman}, it's necessary to allow it to access \file{\~{}mailman}. + Be sure that \file{\~{}mailman} has group writing access and setgid bit is set. Then put the delivering user to \code{mailman} group, and you can - deny access to \file{~mailman} to others. Be sure that you can do the + deny access to \file{\~{}mailman} to others. Be sure that you can do the same with the WWW service. By the way the best thing is to make a virtual mail server to handle all @@ -1125,11 +1125,11 @@ Norbert Bollow (NB). or for automatic list alias handling (when using the lists.kva.hu virtual as above), see \file{contrib/qmail-to-mailman.py} in the Mailman - source distribution. Modify the \file{~mailman/.qmail-default} to + source distribution. Modify the \file{\~{}mailman/.qmail-default} to include: \begin{verbatim} - |/path/to/python /path/to/qmail-to-mailman.py + |preline /path/to/python /path/to/qmail-to-mailman.py \end{verbatim} and new lists will automatically be picked up. @@ -1139,7 +1139,7 @@ Norbert Bollow (NB). \file{/etc/hosts.allow} file: \begin{verbatim} - tcp-env: 127. 10.205.200 : setenv RELAYCLIENT + tcp-env: 127. 10.205.200. : setenv RELAYCLIENT \end{verbatim} where 10.205.200. is your IP address block. If you use tcpserver, then |