aboutsummaryrefslogtreecommitdiffstats
path: root/admin/www/mailman-install/qmail-issues.html
diff options
context:
space:
mode:
Diffstat (limited to 'admin/www/mailman-install/qmail-issues.html')
-rw-r--r--admin/www/mailman-install/qmail-issues.html24
1 files changed, 12 insertions, 12 deletions
diff --git a/admin/www/mailman-install/qmail-issues.html b/admin/www/mailman-install/qmail-issues.html
index 89c90c75..9c2d2ad3 100644
--- a/admin/www/mailman-install/qmail-issues.html
+++ b/admin/www/mailman-install/qmail-issues.html
@@ -66,7 +66,7 @@ Norbert Bollow (NB).
<P>
<em>BN:</em> it highly depends on your mail storing policy. For example
- if you use the simple <span class="file">&nbsp;alias/.qmail-*</span> files, you can use
+ if you use the simple <span class="file">~alias/.qmail-*</span> files, you can use
<b class="program">`id -g alias`</b>. But if you use <span class="file">/var/qmail/users</span>, the
specified mail gid can be used.
@@ -75,19 +75,19 @@ If you are going to be directing virtual domains directly to the
<code>mailman</code> user (using ``virtualdomains'' on a list-only domain, for
example), you will have to use <b class="programopt">--with-mail-gid</b>=<var>gid
of mailman user's group</var>. This is incompatible with having list aliases
- in <span class="file">&nbsp;alias</span>, unless that alias simply forwards to
+ in <span class="file">~alias</span>, unless that alias simply forwards to
<code>mailman-listname*</code>.
<P>
</LI>
<LI>If there is a user <code>mailman</code> on your system, the alias
- <code>mailman-owner</code> will work only in <span class="file">&nbsp;mailman</span>. You have to do
- a <b class="program">touch .qmail-owner</b> in <span class="file">&nbsp;mailman</span> directory to create
+ <code>mailman-owner</code> will work only in <span class="file">~mailman</span>. You have to do
+ a <b class="program">touch .qmail-owner</b> in <span class="file">~mailman</span> directory to create
this alias.
<P>
<em>NB:</em> An alternative, IMHO better solution is to <b class="program">chown
- root&nbsp;mailman</b>, that will stop qmail from considering <code>mailman</code> to
+ root ~mailman</b>, that will stop qmail from considering <code>mailman</code> to
be a user to whom mail can be delivered. (See ``man 8 qmail-getpw''.)
<P>
@@ -116,10 +116,10 @@ where in this case the listname is e.g. <code>zope-users</code>.
<P>
</LI>
<LI><em>BN:</em>If inbound messages are delivered by another user than
- <code>mailman</code>, it's necessary to allow it to access <span class="file">&nbsp;mailman</span>.
- Be sure that <span class="file">&nbsp;mailman</span> has group writing access and setgid bit is
+ <code>mailman</code>, it's necessary to allow it to access <span class="file">~mailman</span>.
+ Be sure that <span class="file">~mailman</span> has group writing access and setgid bit is
set. Then put the delivering user to <code>mailman</code> group, and you can
- deny access to <span class="file">&nbsp;mailman</span> to others. Be sure that you can do the
+ deny access to <span class="file">~mailman</span> to others. Be sure that you can do the
same with the WWW service.
<P>
@@ -155,12 +155,12 @@ For list aliases, you can either create them manually:
<P>
or for automatic list alias handling (when using the lists.kva.hu
virtual as above), see <span class="file">contrib/qmail-to-mailman.py</span> in the Mailman
- source distribution. Modify the <span class="file">&nbsp;mailman/.qmail-default</span> to
+ source distribution. Modify the <span class="file">~mailman/.qmail-default</span> to
include:
<P>
<div class="verbatim"><pre>
- |/path/to/python /path/to/qmail-to-mailman.py
+ |preline /path/to/python /path/to/qmail-to-mailman.py
</pre></div>
<P>
@@ -174,7 +174,7 @@ and new lists will automatically be picked up.
<P>
<div class="verbatim"><pre>
- tcp-env: 127. 10.205.200 : setenv RELAYCLIENT
+ tcp-env: 127. 10.205.200. : setenv RELAYCLIENT
</pre></div>
<P>
@@ -300,7 +300,7 @@ fi
</div>
</div>
<hr />
-<span class="release-info">Release 2.1, documentation updated on December 22, 2004.</span>
+<span class="release-info">Release 2.1, documentation updated on April 10, 2005.</span>
</DIV>
<!--End of Navigation Panel-->