Update of /cvsroot/mailman/mailman
In directory sc8-pr-cvs1:/tmp/cvs-serv25350
Modified Files:
README.POSTFIX
Log Message:
Updated instructions for integration Mailman with Postfix 2.0 (with
some asides for older versions of Postfix).
Index: README.POSTFIX
===================================================================
RCS file: /cvsroot/mailman/mailman/README.POSTFIX,v
retrieving revision 2.16
retrieving revision 2.17
diff -u -d -r2.16 -r2.17
--- README.POSTFIX 13 Sep 2003 22:48:38 -0000 2.16
+++ README.POSTFIX 14 Sep 2003 04:58:35 -0000 2.17
@@ -54,9 +54,8 @@
the case, adjust the instructions according to your use of
configure's --prefix and --with-var-prefix options.
- - If you are using Postfix-style virtual domains and you want
- Mailman to honor your virtual domains, read the section below
- first!
+ - If you are using virtual domains and you want Mailman to honor
+ your virtual domains, read the section below first!
- Add this to the bottom of the $prefix/Mailman/mm_cfg.py file:
@@ -116,29 +115,40 @@
VIRTUAL DOMAINS
- Postfix supports two styles of virtual domains, called
- "Postfix-style" and "Sendmail-style". With the latter, all
- aliases are visible in all domains, and nothing special need be
- done with Mailman.
+ Postfix 2.0 supports "virtual alias domains", essentially what
+ used to be called Postfix-style virtual domains in earlier Postfix
+ versions. To make virtual alias domains work with Mailman, you
+ need to do some setup in both Postfix and Mailman. Mailman will
+ write all virtual alias mappings to a file called, by default,
+ /usr/local/mailman/data/virtual-mailman. It will also use postmap
+ to create the virtual-mailman.db file that Postfix will actually
+ use.
- With Postfix-style virtual domains, things are a little trickier,
- although Mailman should work well with it. First, you'll need to
- add a path to Postfix's virtual_maps variable:
+ First, you need to set up the Postfix virtual alias domains as
+ described in the Postfix documentation (see Postfix's virtual(5)
+ manpage). Note that it's your responsibility to include the
+ "virtual-alias.domain anything" line as described manpage; Mailman
+ will not include this line in virtual-mailman. I highly encourage
+ you to make sure your virtual alias domains are working properly
+ before integrating with Mailman.
- virtual_maps = <your normal virtual files>,
+ Next, add a path to Postfix's virtual_alias_maps variable,
+ pointing to the virtual-mailman file, e.g.:
+
+ virtual_alias_maps = <your normal virtual alias files>,
hash:/usr/local/mailman/data/virtual-mailman
- assuming you've installed Mailman in the default location. Note
- that you must follow Postfix's instructions for setting up the
- virtual domains; get your virtual domains working in Postfix
- first before integrating Mailman.
+ assuming you've installed Mailman in the default location. If
+ you're using an older version of Postfix which doesn't have the
+ virtual_alias_maps variable, use the virtual_maps variable
+ instead.
Next, in your mm_cfg.py file, you will want to set the variable
POSTFIX_STYLE_VIRTUAL_DOMAINS to the list of virtual domains that
- Mailman should update. This may not be all of the virtual domains
- that your Postfix installation supports! The values in this list
- will be matched against the host_name attribute of mailing lists
- objects, and must be an exact match.
+ Mailman should update. This may not be all of the virtual alias
+ domains that your Postfix installation supports! The values in
+ this list will be matched against the host_name attribute of
+ mailing lists objects, and must be an exact match.
Here's an example:
@@ -149,7 +159,8 @@
myhostname = mail.dom1.ain
mydomain = dom1.ain
mydestination = $myhostname, localhost.$mydomain
- virtual_maps = hash:/some/path/to/virtual-dom1,
+ virtual_alias_maps =
+ hash:/some/path/to/virtual-dom1,
hash:/some/path/to/virtual-dom2,
hash:/some/path/to/virtual-dom2
@@ -160,7 +171,7 @@
@dom1.ain @mail.dom1.ain
This tells Postfix to deliver anything addressed to dom1.ain to
- the same mailbox at mail.dom1.com, it's default destination.
+ the same mailbox at mail.dom1.com, its default destination.
In this case you would not include dom1.ain in
POSTFIX_STYLE_VIRTUAL_DOMAINS because otherwise Mailman will write
@@ -170,7 +181,7 @@
[EMAIL PROTECTED] mylist-request
# and so on...
- The more specific entries trump your more general entries and thus
+ The more specific entries trump your more general entries, thus
breaking the delivery of any dom1.ain mailing list.
However, you would include dom2.ain and dom3.ain in mm_cfg.py:
_______________________________________________
Mailman-checkins mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-checkins
