[Workaround] r64 - trunk/sarge
chaas at torf.workaround.org
chaas at torf.workaround.org
Sat Sep 17 21:23:02 CEST 2005
Author: chaas
Date: 2005-09-17 21:23:02 +0200 (Sat, 17 Sep 2005)
New Revision: 64
Modified:
trunk/sarge/en.xml
Log:
Added two new ways to use mailman with virtual domains.
Modified: trunk/sarge/en.xml
===================================================================
--- trunk/sarge/en.xml 2005-09-15 14:38:45 UTC (rev 63)
+++ trunk/sarge/en.xml 2005-09-17 19:23:02 UTC (rev 64)
@@ -1972,40 +1972,70 @@
<para>
A frequently asked question is how to run mailing lists with virtual
- domains using the famous 'mailman' software. Actually this is pretty
- simple. You just have to understand that virtual users cannot have
- piped aliases.
+ domains using the famous 'mailman' software. Actually this is not
+ very hard. There are three ways to accomplish that.
</para>
- <para>
- Piped... what? Well, once you have created a mailing list with the
- 'newlist' command you are requested to add certain aliases to your
- /etc/aliases file like chitchat-admin, chitchat-bounces, chitchat-join
- and so on that point to destinations that look like
- <command>"|/var/lib/mailman/mail/mailman post powerdns-debian"</command>.
- This means that the email is piped into the 'mailman' program.
- Mailman is called and gets the email as input.
- </para>
+ <sect2>
+ <title>Forwarding to local pipes</title>
+ <para>
+ This first approach will use the aliases that you usually insert
+ into <command>/etc/aliases</command>.
+ You just have to understand that virtual users cannot have piped aliases.
+ Piped... what? Well, once you have created a mailing list with the
+ <command>newlist</command> command you are requested to add certain
+ aliases to your /etc/aliases file like chitchat-admin,
+ chitchat-bounces, chitchat-join and so on that point to destinations
+ that look like
+ <command>"|/var/lib/mailman/mail/mailman post powerdns-debian"</command>.
+ This means that the email is piped into the <command>mailman</command>
+ program. Mailman is called and gets the email as input.
+ </para>
- <para>
- This works well for local domains but will fail if you put a piped
- alias like this into a virtual alias. That is because you do not
- have a system user whose user-id you could use to run this pipe.
- So you will have to make a circuit and forward your virtual email
- address to a local email address where you can use piped aliases.
- </para>
+ <para>
+ This works well for local domains but will fail if you put a piped
+ alias like this into a virtual alias. That is because you do not
+ have a system user whose user-id you could use to run this pipe.
+ So you will have to make a circuit and forward your virtual email
+ address to a local email address where you can use piped aliases.
+ </para>
- <para>
- I recommend that you use 'localhost' as your local domain
- (<command>mydestination = localhost</command>) and forward each of the
- mailman aliases to the @localhost equivalent. So if you have a
- chitchat-subscribe at virtual.domain address you just forward it to
- chitchat-subscribe at localhost and use the /etc/aliases as suggested by
- 'mailman'. Perhaps someone comes up with a nifty solution to put
- the /etc/aliases into the MySQL database, too. Let me know if you
- have invented something. :)
- </para>
+ <para>
+ I recommend that you use 'localhost' as your local domain
+ (<command>mydestination = localhost</command>) and forward each of the
+ mailman aliases to the @localhost equivalent. So if you have a
+ chitchat-subscribe at virtual.domain address you just forward it to
+ chitchat-subscribe at localhost and use the /etc/aliases as suggested by
+ 'mailman'. Perhaps someone comes up with a nifty solution to put
+ the /etc/aliases into the MySQL database, too. Let me know if you
+ have invented something. :)
+ </para>
+ </sect2>
+ <sect2>
+ <title>Generic approach using regular expressions</title>
+
+ <para>
+ There is a simple way to use mailman-based mailing lists
+ when you are ready to sacrifice a hostname for mailinglists.
+ Assume your domain is <emphasis>domain.com</emphasis>.
+ You would then use <emphasis>lists.comain.com</emphasis>
+ as the dedicated server name for mailing lists.
+ Please see:
+ <ulink url="http://listes.rezo.net/how.php">http://listes.rezo.net/how.php</ulink>.
+ </para>
+ </sect2>
+
+ <sect2>
+ <title>Using mailman as a transport service</title>
+ <para>
+ The third way to use mailman is to create a transport
+ (one of those services in <command>/etc/postfix/master.cf</command>
+ for mailman. Please see the file
+ <command>/etc/mailman/postfix-to-mailman.py</command> and
+ read the <emphasis>INSTALLATION</emphasis> section of it.
+ </para>
+ </sect2>
</sect1>
<sect1 id="troubleshooting" xreflabel="troubleshooting">
More information about the Workaround-chitchat
mailing list