Update of /cvsroot/mailman/mailman
In directory sc8-pr-cvs1:/tmp/cvs-serv12554
Modified Files:
Tag: Release_2_1-maint
ACKNOWLEDGMENTS INSTALL NEWS README.EXIM README.POSTFIX TODO
Log Message:
Backporting information files from Mailman cvs head.
Index: ACKNOWLEDGMENTS
===================================================================
RCS file: /cvsroot/mailman/mailman/ACKNOWLEDGMENTS,v
retrieving revision 2.43.2.1
retrieving revision 2.43.2.2
diff -u -d -r2.43.2.1 -r2.43.2.2
--- ACKNOWLEDGMENTS 8 Feb 2003 07:13:48 -0000 2.43.2.1
+++ ACKNOWLEDGMENTS 31 Mar 2003 19:07:34 -0000 2.43.2.2
@@ -1,5 +1,5 @@
Mailman - The GNU Mailing List Management System
-Copyright (C) 1998,1999,2000,2001,2002 by the Free Software Foundation, Inc.
+Copyright (C) 1998-2003 by the Free Software Foundation, Inc.
59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
The following folks are or have been the primary maintainers of Mailman:
@@ -58,6 +58,7 @@
Hye-Shik Chang
Paul Cox
Emilio Delgado
+ John Dennis
Stefan Divjak
Maximillian Dornseif
Fred Drake
@@ -79,6 +80,8 @@
Paul Hebble
Tollef Fog Heen
Peer Heinlein
+ Walter Hop
+ Bert Hubert
Henny Huisman
Jeremy Hylton
Ron Jarrell
@@ -133,6 +136,7 @@
John Read
Sean Reifschneider
Christian Reis
+ Ademar de Souza Reis, Jr.
Bernhard Reiter
Stephan Richter
Tristan Roddis
@@ -162,9 +166,11 @@
Kathleen Webb
Ousmane Wilane
Dan Wilder
+ Seb Wills
Michael Yount
Blair Zajac
Noam Zeilberger
+ Todd Zullinger
And everyone else on [EMAIL PROTECTED] and
[EMAIL PROTECTED] Thank you, all.
Index: INSTALL
===================================================================
RCS file: /cvsroot/mailman/mailman/INSTALL,v
retrieving revision 2.19
retrieving revision 2.19.2.1
diff -u -d -r2.19 -r2.19.2.1
--- INSTALL 24 Dec 2002 16:24:21 -0000 2.19
+++ INSTALL 31 Mar 2003 19:07:34 -0000 2.19.2.1
@@ -1,5 +1,5 @@
Mailman - The GNU Mailing List Management System
-Copyright (C) 1998,1999,2000,2001,2002 Free Software Foundation, Inc.
+Copyright (C) 1998-2003 Free Software Foundation, Inc.
59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
This file contains installation instructions for GNU Mailman, which is
@@ -65,7 +65,8 @@
security is based on group-ownership permissions, so it is
important to get this step right. If groupname `mailman' is
already in use, choose something else unique and see the
- --with-groupname below.
+ --with-groupname below. The mailman user created in the
+ previous step must be a member of this group.
- Create an installation directory (called $prefix in the
documentation that follows). All of the Mailman files will be
@@ -315,6 +316,32 @@
Now restart your web server.
+ - Create a "site-wide" mailing list. This is the one that
+ password reminders will appear to come from. Usually this
+ should be the "mailman" mailing list, but if you need to change
+ this, be sure to change the MAILMAN_SITE_LIST variable in
+ mm_cfg.py (see below).
+
+ % bin/newlist mailman
+
+ Follow the prompts, and see the README file for more
+ information.
+
+ Now configure your site list. There is a convenient template
+ for a generic site list in misc/sitelist.cfg to help you with
+ this. The template can be applied to your site list by running:
+
+ % bin/config_list -i data/sitelist.cfg mailman
+
+ Before doing this, review the configuration options in the
+ template (note that many options are not changed by
+ sitelist.cfg). After you do this, be sure you review the
+ configurations via the admin pages for this list.
+
+ Be sure to subscribe yourself to the site list, but use the
+ admin interface because mailback subscription confirmations
+ won't work at this point.
+
- Set up the crontab entries. Mailman runs a number of cron jobs
for its basic functionality. Note that if you're upgrading from
a previous version of Mailman, you'll want to install the new
@@ -387,19 +414,6 @@
to add the following afterwards in the mm_cfg.py file:
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
-
- - Create a "site-wide" mailing list. This is the one that
- password reminders will appear to come from. Usually this
- should be the "mailman" mailing list, but if you need to change
- this, be sure to change the MAILMAN_SITE_LIST variable in
- mm_cfg.py (see below).
-
- % bin/newlist mailman
-
- Follow the prompts, and see the README file for more
- information.
-
- - You should then subscribe yourself to the mailman list.
5. Customize Mailman
Index: NEWS
===================================================================
RCS file: /cvsroot/mailman/mailman/NEWS,v
retrieving revision 2.43.2.2
retrieving revision 2.43.2.3
diff -u -d -r2.43.2.2 -r2.43.2.3
--- NEWS 8 Feb 2003 16:26:20 -0000 2.43.2.2
+++ NEWS 31 Mar 2003 19:07:36 -0000 2.43.2.3
@@ -4,6 +4,9 @@
Here is a history of user visible changes to Mailman.
+2.1.2 (31-Mar-2003)
+
+
2.1.1 (08-Feb-2003)
Lots of bug fixes and language updates. Also:
@@ -19,7 +22,6 @@
the scrubber to remove (and archive) attachments. Otherwise,
attachments would screw up plaintext digests. MIME digests
include the attachments inline.
-
2.1 final (30-Dec-2002)
Index: README.EXIM
===================================================================
RCS file: /cvsroot/mailman/mailman/README.EXIM,v
retrieving revision 2.8
retrieving revision 2.8.2.1
diff -u -d -r2.8 -r2.8.2.1
--- README.EXIM 18 Oct 2002 21:02:15 -0000 2.8
+++ README.EXIM 31 Mar 2003 19:07:37 -0000 2.8.2.1
@@ -99,9 +99,6 @@
user = MAILMAN_USER
group = MAILMAN_GROUP
-(XXX this is untested by me under Exim 3! Can someone using Exim 3
-please let me know if it works?)
-
Director for Exim 3
~~~~~~~~~~~~~~~~~~~
@@ -269,8 +266,6 @@
deny !condition = $header_X-WhitelistedRCPT-nohdrfromcallback:
!verify = header_sender/callout=90s
-
-[XXX all this stuff is completely untested by me! -Greg]
Doing VERP with Exim and Mailman
Index: README.POSTFIX
===================================================================
RCS file: /cvsroot/mailman/mailman/README.POSTFIX,v
retrieving revision 2.11
retrieving revision 2.11.2.1
diff -u -d -r2.11 -r2.11.2.1
--- README.POSTFIX 14 Oct 2002 22:27:18 -0000 2.11
+++ README.POSTFIX 31 Mar 2003 19:07:39 -0000 2.11.2.1
@@ -1,5 +1,5 @@
Mailman - The GNU Mailing List Management System
-Copyright (C) 2001,2002 by the Free Software Foundation, Inc.
+Copyright (C) 2001-2003 by the Free Software Foundation, Inc.
59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
@@ -9,21 +9,33 @@
Postfix installation. As of this writing I've tested it with
Postfix 19991231 up to pl13, and with 200010228 up to pl08.
- It is recommended that you set "owner_request_special = no" in
- your main.cf config file so that Postfix won't treat -owner and
- -request addresses specially (we want Postfix to simply deliver
- such messages to the Mailman wrapper). The default is "yes" I
- believe.
+ By default, Postfix treats -owner and -request addresses
+ specially. Since we want Postfix to deliver such messages to
+ Mailman, you should turn off this option by adding this to your
+ main.cf file:
+
+ owner_request_special = no
In order to support Mailman's optional VERP delivery, you will
want to disable luser_relay (the default) and you will want to set
- recipient_delimiter for extended address semantics. Here, my
- recommendations are to comment out any luser_relay value in your
- main.cf and just go with the defaults. Also, set
- "recipient_delimiter = +" so that the symbol used to separate an
- address from its extended semantics is a + sign. This will work
- well with the default values for VERP_FORMAT and VERP_REGEXP in
- Defaults.py.
+ recipient_delimiter for extended address semantics. You should
+ comment out any luser_relay value in your main.cf and just go with
+ the defaults. Also, add this to your main.cf file:
+
+ recipient_delimiter = +
+
+ Using + as the delimiter works well with the default values for
+ VERP_FORMAT and VERP_REGEXP in Defaults.py.
+
+ When attempting to deliver a message to a non-existent local
+ address, Postfix may return a 450 error code. Since this is a
+ non-transient error code, Mailman will continue to attempt to
+ delivery the message for DELIVERY_RETRY_PERIOD (5 days by
+ default). You might want to set Postfix up so that it returns
+ permanent error codes for non-existent local users by adding the
+ following to your main.cf file:
+
+ unknown_local_recipient_reject_code = 550
Finally, if you are using Postfix-style virtual domains, read the
section on virtual domain support below.
@@ -98,7 +110,7 @@
that it will take about a minute for Postfix to notice the change
to the aliases.db file and update its tables. I consider this a
minor inconvenience.
-
+
VIRTUAL DOMAINS
@@ -160,7 +172,7 @@
breaking the delivery of any dom1.ain mailing list.
However, you would include dom2.ain and dom3.ain in mm_cfg.py:
-
+
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['dom2.ain', 'dom3.ain']
Now, any list that Mailman creates in either of those two domains,
Index: TODO
===================================================================
RCS file: /cvsroot/mailman/mailman/TODO,v
retrieving revision 2.15
retrieving revision 2.15.2.1
diff -u -d -r2.15 -r2.15.2.1
--- TODO 19 Nov 2002 06:50:54 -0000 2.15
+++ TODO 31 Mar 2003 19:07:40 -0000 2.15.2.1
@@ -1,5 +1,5 @@
Mailman - The GNU Mailing List Management System
-Copyright (C) 1998,1999,2000,2001,2002 by the Free Software Foundation, Inc.
+Copyright (C) 1998-2003 by the Free Software Foundation, Inc.
59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
@@ -7,8 +7,8 @@
(Last Update: $Date$)
Here's the wish list for future versions of Mailman. Many new
- features have been added to Mailman 2.1, so what's left will
- probably end up in a Mailman 3.0.
+ features have been added to Mailman 2.1, and it is currently
+ undecided whether the next release will be 2.2 or 3.0.
Please also see the Mailman design notes wiki at
_______________________________________________
Mailman-checkins mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-checkins