mailman-2.1.29/ACKNOWLEDGMENTS0000644000000000000000000001240013325720670013523 0ustar 00000000000000Mailman - The GNU Mailing List Management System Copyright (C) 1998-2018 by the Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA The following folks are or have been core developers of Mailman (in reverse alphabetical order): Barry Warsaw, Mailman's yappy guard dog Thomas Wouters, Mailman's Dutch treat John Viega, Mailman's inventor Mark Sapiro, Mailman's compulsive responder Harald Meland, Norse Mailman Ken Manheimer, Mailman's savior Tokio Kikuchi, Mailman's weatherman Scott Cotton, Cookie-Monster They can be contacted directly via mailman-cabal@python.org. Here is the list of other contributors who have donated large bits of code, and have assigned copyright for contributions to the FSF: Juan Carlos Rey Anaya Richard Barrett Stephan Berndts Norbert Bollow Ben Gertzfield Victoriano Giralt Mads Kiilerich The Dragon De Monsyne Les Niles Terri Oda Simone Piunno Thanks also go to the following people for their important contributions in other aspects of the Mailman project: Brad Knowles JC Dill Thanks also to Dragon for his winning Mailman logo contribution, and to Terri Oda for the neat shortcut icon and the member documentation. Control.com sponsored development of several Mailman 2.1 features, including topics filters, external membership sources, and initial virtual mailing list support. My thanks especially to Dan Pierson and Ken Crater from Control.com. Here is the list of other people who have contributed useful ideas, suggestions, bug fixes, testing, etc., or who have been very helpful in answering questions on mailman-users. David Abrahams William Ahern Terry Allen Jose Paulo Moitinho de Almeida Sven Anderson Matthias Andree Anton Antonov Mike Avery Stonewall Ballard Moreno Baricevic Jeff Berliner Stuart Bishop David Blomquist Bojan Søren Bondrup Grant Bowman Alessio Bragadini J. D. Bronson Stan Bubrouski Daniel Buchmann Ben Burnett Ted Cabeen Mentor Cana John Carnes Julio A. Cartaya Claudio Cattazzo Donn Cave David Champion Hye-Shik Chang Eric D. Christensen Tom G. Christensen Paul Cox Stefaniu Criste Robert Daeley Ned Dawes Emilio Delgado John Dennis Stefan Divjak Maximillian Dornseif Fred Drake Maxim Dzumanenko Piarres Beobide Egaña Rob Ellis Kerem Erkan Fil Patrick Finnerty Bob Fleck Erik Forsberg Darrell Fuhriman Robert Garrigós Carson Gaspar Pascal GEORGE Vadim Getmanshchuk David Gibbs Dmitri I GOULIAEV Terry Grace Federico Grau Pekka Haavisto David Habben Stig Hackvan Jeff Hahn Terry Hardie Paul Hebble Tollef Fog Heen Peer Heinlein James Henstridge Walter Hop Bert Hubert Henny Huisman Jeremy Hylton Ikeda Soji Rostyk Ivantsiv Ron Jarrell Matthias Juchem Tamito KAJIYAMA Nino Katic SHIGENO Kazutaka Ashley M. Kirchner Matthias Klose Harald Koch Eddie Kohler Chris Kolar Uros Kositer Andrew Kuchling Ricardo Kustner L'homme Moderne Sylvain Langlade Ed Lau J C Lawrence Greg Lindahl Christopher P. Lindsey Martin von Loewis Dario Lopez-Kästen Tanner Lovelace Jay Luker Gergely Madarasz Luca Maranzano John A. Martin Andrew Martynov Jason R. Mastaler Michael Mclay Michael Meltzer Marc MERLIN Nigel Metheringham Dan Mick Garey Mills Martin Mokrejs Michael Fischer v. Mollard David Martínez Moreno Dirk Mueller Jonas Muerer Erik Myllymaki Balazs Nagy Moritz Naumann Dale Newfield Hrvoje Niksic Les Niles Mike Noyes David B. O'Donnell Timothy O'Malley "office" Dan Ohnesorg Gerald Oskoboiny Eva Österlind Toni Panadès Jon Parise Chris Pepper Tim Peters Joe Peterson PieterB Rodolfo Pilas Skye Poier Martin Pool Don Porter Francesco Potortì Bob Puff Michael Ranner John Read Sean Reifschneider Christian Reis Ademar de Souza Reis, Jr. Bernhard Reiter Stephan Richter Tristan Roddis Heiko Rommel Luigi Rosa Guido van Rossum Nicholas Russo Chris Ryan Cabel Sasser Bartosz Sawicki Kai Schaetzl Karoly Segesdi Gleydson Mazioli da Silva Pasi Sjöholm Chris Snell Mikhail Sobolev Greg Stein Dale Stimson Students of HIT Szabolcs Szigeti Vizi Szilard David T-G Owen Taylor Danny Terweij Jim Tittsler Todd (Freedom Lover) Roger Tsang Chuq Von Rospach Jens Vagelpohl Valia V. Vaneeva Anti Veeranna Todd Vierling Bill Wagner Greg Ward Mark Weaver Kathleen Webb Florian Weimer Ousmane Wilane Dan Wilder Seb Wills Dai Xiaoguang Ping Yeh YASUDA Yukihiro Michael Yount Blair Zajac Mikhail Zabaluev Noam Zeilberger Daniel Zeiss Todd Zullinger And everyone else on mailman-developers@python.org and mailman-users@python.org! Thank you, all. Local Variables: mode: indented-text indent-tabs-mode: nil End: mailman-2.1.29/BUGS0000644000000000000000000000064713325720670012050 0ustar 00000000000000Mailman - The GNU Mailing List Management System Copyright (C) 1998-2018 by the Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA The Mailman project is being managed on Launchpad at https://launchpad.net/mailman You should submit bugs to the Launchpad bug manager at https://bugs.launchpad.net/mailman If you have a suggested fix, please attach it to your bug report. mailman-2.1.29/FAQ0000644000000000000000000003531613325720670011720 0ustar 00000000000000Mailman - The GNU Mailing List Management System Copyright (C) 1998-2018 by the Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA Note: We've migrated the FAQ to the wiki at http://wiki.list.org/ To see the Mailman FAQ go to http://wiki.list.org/x/AgA3 FREQUENTLY ASKED QUESTIONS Q. How do you spell this program? A. You spell it "Mailman", with a leading capital "M" and a lowercase second "m". It is incorrect to spell it "MailMan" (i.e. you should not use StudlyCaps). Q. I'm getting really terrible performance for outgoing messages. It seems that if the MTA has trouble resolving DNS for any recipients, qrunner just gets really slow clearing the queue. Any ideas? A. What's likely happening is that your MTA is doing DNS resolution on recipients for messages delivered locally (i.e. from Mailman to your MTA via SMTPDirect.py). This is a Bad Thing. You need to turn off synchronous DNS resolution for messages originating from the local host. In Exim, the value to edit is receiver_verify_hosts. Consult the Mailman Installation Manual for details. Other MTAs have (of course) different parameters and defaults that control this. First check the README file for your MTA and then consult your MTA's own documentation. Q. My list members are complaining about Mailman's List-* headers! What can I do about this? A. These headers are described in RFC 2369 and are added by Mailman for the long-term benefit of end-users. While discouraged, the list admin can disable these via the General Options page. See also README.USERAGENT for more information. Q. Can I put the user's address in the footer that Mailman adds to each message? A. Yes, in Mailman 2.1. The site admin needs to enable personalization by setting the following variable in the mm_cfg.py file: OWNERS_CAN_ENABLE_PERSONALIZATION = Yes Once this is done, list admins can enable personalization for regular delivery members (digest deliveries can't be personalized currently). A personalized list can include the user's address in the footer. Q. My users hate HTML in their email and for security reasons, I want to strip out all MIME attachments. How can I do this? A. Mailman 2.1 has this feature built-in. See the Content Filtering Options page in the admin interface. Q. What if I get "document contains no data" from the web server, or mail isn't getting delivered, or I see "Premature end of script headers" or "Mailman CGI error!!!" A. The most likely cause of this is that the GID that is compiled into the C wrappers does not match the GID that your Web server invokes CGI scripts with. Note that a similar error could occur if your mail system invokes filter programs under a GID that does not match the one compiled into the C mail wrapper. To fix this you will need to re-configure Mailman using the --with-cgi-gid and --with-mail-gid options. See the INSTALL file for details. These errors are logged to syslog and they do not show up in the Mailman log files. Problems with the CGI wrapper do get reported in the web browser though (unless STEALTH_MODE is enabled), and include the expected GID, so that should help a lot. You may want to have syslog running and configured to log the mail.error log class somewhere; on Solaris systems, the line mail.debug /var/log/syslog causes the messages to go to them in /var/log/syslog, for example. (The distributed syslog.conf forwards the message to the loghost, when present. See the syslog man page for more details.) If your system is set up like this, and you get a failure trying to visit the mailman/listinfo web page, and it's due to a UID or GID mismatch, then you should get an entry at the end of /var/log/syslog identifying the expected and received values. If you are not getting any log messages in syslog, or in Mailman's own log files, but messages are still not being delivered, then it is likely that qrunner is not running (qrunner is the process that handles all mail in the system). In Mailman 2.0, qrunner was invoked from cron so make sure your crontab entries for the `mailman' user have been installed. In Mailman 2.1, qrunner is started with the bin/mailmanctl script, which can be invoked manually, or merged with your OS's init scripts. Q. What should I check periodically? A. Many of the scripts have their standard error logged to $prefix/logs/error, and some of the modules write caught errors there, as well, so you should check there at least occasionally to look for bugs in the code and problems in your setup. You may want to periodically check the other log files in the logs/ directory, perhaps occasionally rotating them with something like the Linux logrotate script. Q. I can't access the public archives. Why? A. If you are using Apache, you must make sure that FollowSymLinks is enabled for the path to the public archives. Note that the actual archives always reside in the private tree, and only when archives are public, is the symlink followed. See this archive message for more details: http://mail.python.org/pipermail/mailman-users/1998-November/000150.html Q. Still having problems? Running QMail? A. Make sure that you are using "preline" before calling the "mailman" wrapper: |preline /home/mailman/mail/mailman post listname "preline" adds a Unix-style "From " header which the archiver requires. You can fix the archive mbox files by adding: From somebody Mon Oct 9 12:27:34 MDT 2000 before every message and re-running the archive command "bin/arch listname". The archives should now exist. Q. I want to get rid of some messages in my archive. How do I do this? A. David Rocher posts the following recipe: * remove $prefix/archives/private/ * edit $prefix/archives/private/.mbox/.mbox [optional] * run $prefix/bin/arch Q. How secure are the authentication mechanisms used in Mailman's web interface? A. If your Mailman installation run on an SSL-enabled web server (i.e. you access the Mailman web pages with "https://..." URLs), you should be as safe as SSL itself is. However, most Mailman installation run under standard, encryption-unaware servers. There's nothing wrong with that for most applications, but a sufficiently determined cracker *could* get unauthorized access by: * Packet sniffing: The password used to do the initial authentication for any non-public Mailman page is sent as clear text over the net. If you consider this to be a big problem, you really should use an SSL-enabled server. * Stealing a valid cookie: After successful password authentication, Mailman sends a "cookie" back to the user's browser. This cookie will be used for "automatic" authentication when browsing further within the list's protected pages. Mailman employs "session cookies" which are set until you quit your browser or explicitly log out. Gaining access to the user's cookie (e.g. by being able to read the user's browser cookie database, or by means of packet sniffing, or maybe even by some broken browser offering all it's cookies to any and all sites the user accesses), and at the same time being able to fulfill the other criteria for using the cookie could result in unauthorized access. Note that this problem is more easily exploited when users browse the web via proxies -- in that case, the cookie would be valid for any connections made through that proxy, and not just for connections made from the particular machine the user happens to be accessing the proxy from. * Getting access to the user's terminal: This is really just another kind of cookie stealing. The short cookie expiration time is supposed to help defeat this problem. It can be considered the price to pay for the convenience of not having to type the password in every time. Q. I want to backup my lists. What do I need to save? A. See this FAQ entry: http://wiki.list.org/x/5oA9 Q. How do I rename a list? A. Renaming a list is currently a bit of a pain to do completely correctly, especially if you want to make sure that the old list contacts are automatically forwarded to the new list. This ought to be easier. :( The biggest problem you have is how to stop mail and web traffic to your list during the transition, and what to do about any mail undelivered to the old list after the move. I don't think there are any foolproof steps, but here's how you can reduce the risk: - Temporarily disable qrunner. To do this, you need to edit the user `mailman's crontab entry. Execute the following command, commenting out the qrunner line when you're dropped into your editor. Then save the file and quit the editor. % crontab -u mailman -e - Turn off your mail server. This is mostly harmless since remote MTAs will just keep retrying until you turn it back on, and it's not going to be off for very long. - Next turn off your web server if possible. This of course means your entire site will be off-line while you make the switch and this may not be acceptable to you. The next best suggestion is to set up your permanent redirects now for the list you're moving. This means that anybody looking for the list under its old name will be redirected to the new name, but they'll get errors until you've completed the move. Let's say the old name is "oldname" and the new name is "newname". Here are some Apache directives that will do the trick, though YMMV: RedirectMatch permanent /mailman/(.*)/oldname(.*) http://www.dom.ain/mailman/$1/newname$2 RedirectMatch permanent /pipermail/oldname(.*) http://www.dom.ain/pipermail/newname$1 Add these to your httpd.conf file and restart Apache. - Now cd to the directory where you've installed Mailman. Let's say it's /usr/local/mailman: % cd /usr/local/mailman and cd to the `lists' subdirectory: % cd lists You should now see the directory `oldname'. Move this to `newname': % mv oldname newname - Now cd to the private archives directory: % cd ../archives/private You will need to move the oldname's .mbox directory, and the .mbox file within that directory. Don't worry about the public archives; the next few steps will take care of them without requiring you to fiddle around in the file system: % mv oldname.mbox newname.mbox % mv newname.mbox/oldname.mbox newname.mbox/newname.mbox - You now need to run the `bin/move_list' script to update some of the internal archiver paths. IMPORTANT: Skip this step if you are using Mailman 2.1! % cd ../.. % bin/move_list newname - You should now regenerate the public archives: % bin/arch newname - You'll likely need to change some of your list's configuration options, especially if you want to accept postings addressed to the old list on the new list. Visit the admin interface for your new list: o Go to the General options o Change the "real_name" option to reflect the new list's name, e.g. "Newname" o Change the subject prefix to reflect the new list's name, e.g. "[Newname] " (yes, that's a trailing space character). o Optionally, update other configuration fields like info, description, or welcome_msg. YMMV. o Save your changes o Go to the Privacy options o Add the old list's address to acceptable_aliases. E.g. "oldname@dom.ain". This way, (after the /etc/aliases changes described below) messages posted to the old list will not be held by the new list for "implicit destination" approval. o Save your changes - Now you want to update your /etc/aliases file to include the aliases for the new list, and forwards for the old list to the new list. Note that these instructions are for Sendmail style alias files, adjust to the specifics of how your MTA is set up. o Find the lines defining the aliases for your old list's name o Copy and paste them just below the originals. o Change all the references of "oldname" to "newname" in the pasted stanza. o Now change the targets of the original aliases to forward to the new aliases. When you're done, you will end up with /etc/aliases entries like the following (YMMV): XXX This needs updating for MM2.1! # Forward the oldname list to the newname list oldname: newname@dom.ain oldname-request: newname-request@dom.ain oldname-admin: newname-admin@dom.ain oldname-owner: newname-owner@dom.ain newname: "|/usr/local/mailman/mail/mailman post newname" newname-admin: "|/usr/local/mailman/mail/mailman mailowner newname" newname-request: "|/usr/local/mailman/mail/mailman mailcmd newname" newname-owner: newname-admin o Run newaliases - Before you restart everything, you want to make one last check. You're looking for files in the qfiles/ directory that may have been addressed to the old list but weren't delivered before you renamed the list. Do something like the following: % cd /usr/local/mailman/qfiles % grep oldname *.msg If you get no hits, skip to the next step, you've got nothing to worry about. If you did get hits, then things get complicated. I warn you that the rest of this step is untested. :( For each of the .msg files that were destined for the old list, you need to change the corresponding .db file. Unfortunately there's no easy way to do this. Anyway... Save the following Python code in a file called 'hackdb.py': -------------------------hackdb.py import sys import marshal fp = open(sys.argv[1]) d = marshal.load(fp) fp.close() d['listname'] = sys.argv[2] fp = open(sys.argv[1], 'w') marshal.dump(d, fp) fp.close() ------------------------- And then for each file that matched your grep above, do the following: % python hackdb.py reallylonghexfilenamematch1.db newname - It's now safe to turn your MTA back on. - Turn your qrunner back on by running % crontab -u mailman -e again and this time uncommenting the qrunner line. Save the file and quit your editor. - Rejoice, you're done. Send $100,000 in shiny new pennies to the Mailman cabal as your downpayment toward making this easier for the next list you have to rename. :) Local Variables: mode: text indent-tabs-mode: nil End: mailman-2.1.29/INSTALL0000644000000000000000000000144613325720670012414 0ustar 00000000000000Mailman - The GNU Mailing List Management System Copyright (C) 1998-2018 Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA The installation and upgrading instructions are now completely contained in the Mailman Installation Guide. Web, PostScript, PDF, and plaintext formats for this guide are available both within this source distribution and online. All manuals within this source distribution are provided in the doc/ directory: HTML : doc/mailman-install/index.html PostScript : doc/mailman-install.ps PDF : doc/mailman-install.pdf plain text : doc/mailman-install.txt Or go online at http://www.list.org/site.html to find the online installation guide. Local Variables: mode: indented-text indent-tabs-mode: nil End: mailman-2.1.29/Mailman/0000755000000000000000000000000013325720670012734 5ustar 00000000000000mailman-2.1.29/Makefile.in0000644000000000000000000001014113325720670013420 0ustar 00000000000000# Copyright (C) 1998-2018 by the Free Software Foundation, Inc. # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. # NOTE: Makefile.in is converted into Makefile by the configure script # in the parent directory. Once configure has run, you can recreate # the Makefile by running just config.status. # Variables set by configure SHELL= /bin/sh VPATH= @srcdir@ srcdir= @srcdir@ bindir= @bindir@ prefix= @prefix@ exec_prefix= @exec_prefix@ var_prefix= @VAR_PREFIX@ DESTDIR= CC= @CC@ INSTALL= @INSTALL@ PYTHON= @PYTHON@ DEFS= @DEFS@ # Customizable but not set by configure OPT= @OPT@ CFLAGS= @CFLAGS@ $(OPT) $(DEFS) VAR_DIRS= \ logs archives lists locks data spam qfiles \ archives/private archives/public ARCH_INDEP_DIRS= \ bin templates scripts cron pythonlib \ Mailman Mailman/Cgi Mailman/Logging Mailman/Archiver \ Mailman/Handlers Mailman/Queue Mailman/Bouncers \ Mailman/MTA Mailman/Gui Mailman/Commands messages icons \ tests tests/bounces tests/msgs ARCH_DEP_DIRS= cgi-bin mail # Directories make should decend into SUBDIRS= bin cron misc Mailman scripts src templates messages tests # Modes for directories and executables created by the install # process. Default to group-writable directories but # user-only-writable for executables. DIRMODE= 775 EXEMODE= 755 FILEMODE= 644 INSTALL_PROGRAM=$(INSTALL) -m $(EXEMODE) DIRSETGID= chmod g+s DATE = $(shell python -c 'import time; print time.strftime("%d-%b-%Y"),') LANGPACK = README-I18N.en templates messages EXCLUDES = --exclude=CVS --exclude=.cvsignore --exclude=Makefile* --exclude=*.files --exclude=*.old # Rules all: subdirs subdirs: $(SUBDIRS) for d in $(SUBDIRS); \ do \ (cd $$d; $(MAKE)); \ done install: doinstall update doinstall: $(SUBDIRS) @echo "Creating architecture independent directories..." @for d in $(VAR_DIRS); \ do \ dir=$(DESTDIR)$(var_prefix)/$$d; \ if test ! -d $$dir; then \ echo "Creating directory hierarchy $$dir"; \ $(srcdir)/mkinstalldirs $$dir; \ chmod $(DIRMODE) $$dir; \ $(DIRSETGID) $$dir; \ else true; \ fi; \ done chmod o-r $(DESTDIR)$(var_prefix)/archives/private @for d in $(ARCH_INDEP_DIRS); \ do \ dir=$(DESTDIR)$(prefix)/$$d; \ if test ! -d $$dir; then \ echo "Creating directory hierarchy $$dir"; \ $(srcdir)/mkinstalldirs $$dir; \ chmod $(DIRMODE) $$dir; \ $(DIRSETGID) $$dir; \ else true; \ fi; \ done @echo "Creating architecture dependent directories..." @for d in $(ARCH_DEP_DIRS); \ do \ dir=$(DESTDIR)$(exec_prefix)/$$d; \ if test ! -d $$dir; then \ echo "Creating directory hierarchy $$dir"; \ $(srcdir)/mkinstalldirs $$dir; \ chmod $(DIRMODE) $$dir; \ $(DIRSETGID) $$dir; \ else true; \ fi; \ done @for d in $(SUBDIRS); \ do \ (cd $$d; $(MAKE) DESTDIR=$(DESTDIR) install); \ done $(PYTHON) -c 'from compileall import *; compile_dir("$(DESTDIR)$(prefix)/Mailman", ddir="$(prefix)/Mailman")' # Only run bin/update if we aren't installing in DESTDIR, as this # means there are probably no lists to deal with, and it wouldn't # work anyway (because of import paths.) update: @(cd $(DESTDIR)$(prefix) ; test -n "$(DESTDIR)" || bin/update) clean: $(SUBDIRS) @for d in $(SUBDIRS); \ do \ (cd $$d; $(MAKE) clean); \ done -rm -f update.log distclean: $(SUBDIRS) @for d in $(SUBDIRS); \ do \ (cd $$d; $(MAKE) distclean); \ done -rm -f config.cache config.log config.status Makefile -rm -rf build langpack: tar zcvf langpack-$(DATE).tgz $(EXCLUDES) $(LANGPACK) mailman-2.1.29/NEWS0000644000000000000000000061710313325720670012065 0ustar 00000000000000-*- coding: iso-8859-1 -*- Mailman - The GNU Mailing List Management System Copyright (C) 1998-2018 by the Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA Here is a history of user visible changes to Mailman. 2.1.29 (24-Jul-2018) Bug Fixes - Fixed the listinfo and admin overview pages that were broken by LP: #1780874. (LP: #1783417) 2.1.28 (23-Jul-2018) Security - A content spoofing vulnerability with invalid list name messages in the web UI has been fixed. CVE-2018-13796 (LP: #1780874) New Features - It is now possible to edit HTML and text templates via the web admin UI in a supported language other than the list's preferred_language. Thanks to Yasuhito FUTATSUKI. i18n - The Japanese translation has been updated by Yasuhito FUTATSUKI. - The German translation has been updated by Ralf Hildebrandt. - The Esperanto translation has been updated by Rubén Fernández Asensio. Bug fixes and other patches - The BLOCK_SPAMHAUS_LISTED_DBL_SUBSCRIBE feature added in 2.1.27 was not working. This is fixed. (LP: #1779774) - Escaping of HTML entities for the web UI is now done more selectively. (LP: #1779445) 2.1.27 (22-Jun-2018) Security - Existing protections against malicious listowners injecting evil scripts into listinfo pages have had a few more checks added. JVN#00846677/JPCERT#97432283/CVE-2018-0618 - A few more error messages have had their values HTML escaped. JVN#00846677/JPCERT#97432283/CVE-2018-0618 - The hash generated when SUBSCRIBE_FORM_SECRET is set could have been the same as one generated at the same time for a different list and IP address. While this is not thought to be exploitable in any way, the generation has been changed to avoid this. Thanks to Ralf Jung. New Features - An option has been added to bin/add_members to issue invitations instead of immediately adding members. (LP: #1773064) - A new BLOCK_SPAMHAUS_LISTED_IP_SUBSCRIBE setting has been added to enable blocking web subscribes from IPv4 addresses listed in Spamhaus SBL, CSS or XBL. It will work with IPv6 addresses if Python's py2-ipaddress module is installed. The module can be installed via pip if not included in your Python. - Thanks to Jim Popovitch, Mailman has a new 'security' log and logs authentication failures to the various web CGI functions. The logged data include the remote IP and can be used to automate blocking of IPs with something like fail2ban. Since Mailman 2.1.14, these have returned an http 401 status and the information should be logged by the web server, but this new log makes that more convenient. Also, the 'mischief' log entries for 'hostile listname' noe include the remote IP if available. - Thanks to Jim Popovitch, admin notices of (un)subscribes now may give the source of the action. This consists of a %(whence)s replacement that has been added to the admin(un)subscribeack.txt templates. Thanks to Yasuhito FUTATSUKI for updating the non-English templates and help with internationalizing the reasons. - Thanks to Jim Popovitch, there is a new BLOCK_SPAMHAUS_LISTED_DBL_SUBSCRIBE setting to enable blocking web subscribes for addresses in domains listed in the Spamhaus DBL. i18n - The Japanese translation has been updated by Yasuhito FUTATSUKI. - The Russian translation has been updated by Danil Smirnov. - A partial Esperanto translation has been added. Thanks to Rubén Fernández Asensio. - Fixed a '# -*- coding:' line in the Russian message catalog that was mistakenly translated to Russian. (LP: #1777342) Bug fixes and other patches - Some messages from bin/arch were not issued in the charset of the system locale when DISABLE_COMMAND_LOCALE_CSET is No. Thanks to Yasuhito FUTATSUKI this is now fixed. (LP: #1768892) - The message displayed in the browser when accessing a Mailman CGI when mm_cfg.py can't be imported due to some exception other than ImportError has been improved. (LP: #1760506) - The reimplementation of DELIVERY_RETRY_WAIT in 2.1.26 could cause extra dequeueing and requeueing in the out queue by OutgoingRunner. This is fixed. (LP: #1762871) - A Python 2.7 dependency introduced in the ToDigests handler in Mailman 2.1.24 has been removed. (LP: #1755317) - Bad values in a list's topics will no longer break everything that might instantiate the list. (LP: #1754516) - A Python 2.7 dependency introduced with the reCAPTCHA feature in 2.1.26 has been removed. (LP: #1752658) - The reCAPTCHA feature requires JavaScript. If JavaScript is not enabled, a message will be displayed on the subscribe form that JavaScript is required. (LP: #1769374) - Quoting in the mailman-config command has been changed from double to single quotes to allow double-quoted parameters. (LP: #1774986) - Approving a held subscription for a user with a 'different' preferred language no longer corrupts the results page. (LP: #1777222) - An issue with garbled descriptions on listinfo and admin overview pages and the heading of a list's listinfo page due to incompatible character sets has been fixed thanks to Yasuhito FUTATSUKI. Miscellaneous - Added to the contrib directory, a script from Jim Popovitch to generate Sitemap files for a list's archive. 2.1.26 (04-Feb-2018) Security - An XSS vulnerability in the user options CGI could allow a crafted URL to execute arbitrary javascript in a user's browser. A related issue could expose information on a user's options page without requiring login. These are fixed. Thanks to Calum Hutton for the report. CVE-2018-5950 (LP: #1747209) New Features - Thanks to David Siebörger who adapted an existing patch by Andrea Veri to use Google reCAPTCHA v2 there is now the ability to add reCAPTCHA to the listinfo subscribe form. There are two new mm_cfg.py settings for RECAPTCHA_SITE_KEY and RECAPTCHA_SECRET_KEY, the values for which you obtain for your domain(s) from Google at . - Thanks to Lindsay Haisley, there is a new bin/mailman-config command to display various information about this Mailman version and how it was configured. i18n - The Japanese message catalog has been updated for added strings by Yasuhito FUTATSUKI. - The German translation of a couple of templates has been updated by Thomas Hochstein. - The Japanese translation of Defaults.py.in has been updated by Yasuhito FUTATSUKI. Bug fixes and other patches - Fixed an i18n bug in the reCAPTCHA feature. (LP: #1746189) - Added a few more environment variables to the list of those passed to CGIs to support an nginx/uwsgi configuration. (LP #1744739) - Mailman 2.1.22 introduced a Python 2.7 dependency that could affect bin/arch processing a message without a valid Date: header. The dependency has been removed. (LP: #1740543) - Messages held for header_filter_rules now show the matched regexp in the hold reason. (LP: #1737371) - When updating the group and mode of a .db file with Mailman's Postfix integration, a missing file is ignored. (LP: #1734162) - The DELIVERY_RETRY_WAIT setting is now effective. (LP: #1729472) 2.1.25 (26-Oct-2017) New Features - The admindb held subscriptions listing now includes the date of the most recent request from the address. (LP: #1697097) Accessibility - The admin Membership List now includes text for screen readers which identifies the function of each checkbox. CSS is added to the page to visually hide the text but still allow screen readers to read it. Similar text has been added to some radio buttons on the admindb pages. i18n - The Russian translation has been updated by Sergey Matveev. (LP: #1708016) Bug fixes and other patches - Thanks to Jim Popovitch, certain failures in DNS lookups of DMARC policy will now result in mitigations being applied. (LP: #1722013) - The default DMARC reject reason now properly replaces %(listowner)s. (LP: #1718962) - The web roster page now shows case preserved email addresses. (LP: #1707447) - Changed the SETGID wrappers to only pass those items in the environment that are needed by the called scripts. (LP: #1705736) - Fixed MTA/Postfix.py to ensure that created aliases(.db) and virtual-mailman(.db) files are readable by Postfix and the .db files are owned by the Mailman user. (LP: #1696066) - Defended against certain web attacks that cause exceptions and "we hit a bug" responses when POST data or query fragments contain multiple values for the same parameter. (LP: #1695667) - The fix for LP: #1614841 caused a regression in the options CGI. This has been fixed. (LP: #1602608) - Added a -a option to the (e)grep commands in contrib/mmdsr to account for logs that may have non-ascii and be seen as binary. - Fixed the -V option to bin/list_lists to not show lists whose host is a subdomain of the given domain. (LP: #1695610) 2.1.24 (02-Jun-2017) Security - A most likely unexploitable XSS attach that relies on the Mailman web server passing a crafted Host: header to the CGI environment has been fixed. Apache for one is not vulnerable. Thanks to Alqnas Eslam. New Features - There is a new RCPT_BASE64_HEADER_NAME setting. If this is set to a non-empty string, that string is the name of a header that will be added to personalized and VERPed deliveries with value equal to the base64 encoding of the recipient's email address. This is intended to enable identification of the recipient otherwise redacted from "spam report" feedback loop messages. - cron/senddigests has a new -e/--exceptlist option to send pending digests for all but a named list. (LP: #1619770) - The values for DEFAULT_DIGEST_FOOTER and DEFAULT_MSG_FOOTER have been changed to use a standard signature separator for DEFAULT_MSG_FOOTER and to remove the unneded line of underscores from DEFAULT_DIGEST_FOOTER. (LP: #266269) i18n - The Polish html templates have been recoded to use html entities instead of non-ascii characters. - The Basque (Euskara) translation has been updated by Gari Araolaza. - The German "details for personalize" page has been updated by Christian F Buser. - The Japanese translation has been updated by Yasuhito FUTATSUKI. Bug fixes and other patches - The list-owner@virtual.domain addresses are now added to virtual-mailman as they are exposed in 'list created' emails. (LP: #1694384) - The 'list run by' addresses in web page footers are now just the list-owner address. (LP: #1694384) - Changed member_verbosity_threshold from a >= test to a strictly > test to avoid the issue of moderating every post when the threshold = 1. (LP: #1693366) - Subject prefixing has been improved to always have a space between the prefix and the subject even with non-ascii in the prefix. This will sometimes result in two spaces when the prefix is non-ascii but the subject is ascii, but this is the lesser evil. (LP: #1525954) - Treat message and digest headers and footers as empty if they contain only whitespace. (LP: #1673307) - Ensured that added message and digest headers and footers always have a terminating new-line. (LP: #1670033) - Fixed an uncaught TypeError in the subscribe CGI. (LP: #1667215) - Added recognition for a newly seen mailEnable bounce. - Fixed an uncaught NotAMemberError when a member is removed before a probe bounce for the member is returned. (LP: #1664729) - Fixed a TypeError thrown in the roster CGI when called with a listname containing a % character. (LP: #1661810) - Fixed a NameError issue in bin/add_members with DISABLE_COMMAND_LOCALE_CSET = yes. (LP: #1647450) - The CleanseDKIM handler has been removed from OWNER_PIPELINE. It isn't needed there and has adverse DMARC implications for messages to -owner of an anonymous list. (LP: #1645901) - Fixed an issue with properly RFC 2047 encoding the display name in the From: header for messages with DMARC mitigations. (LP: #1643210) - Fixed an issue causing UnicodeError in sending digests following a change of a list's preferred_language. (LP: #1644356) - Enhanced the fix for race conditions in MailList().Load(). (LP: #266464) - Fixed a typo in Utils.py that could have resulted in a NameError in logging an unlikely occurrence. (LP: #1637745) - Fixed a bug which created incorrect "view more members" links at the bottom of the admin Membership List pages. (LP: #1637061) - The 2.1.23 fix for LP: #1604544 only fixed the letter links at the top of the Membership List. The links at the bottom have now been fixed. - paths.py now adds dist-packages as well as site-packages to sys.path. (LP: #1621172) - INIT INFO has been added to the sample init.d script. (LP: #1620121) 2.1.23 (27-Aug-2016) Security - CSRF protection has been extended to the user options page. This was actually fixed by Tokio Kikuchi as part of the fix for LP: #775294 and intended for Mailman 2.1.15, but that fix wasn't completely merged at the time. The full fix also addresses the admindb, and edithtml pages as well as the user options page and the previously fixed admin pages. Thanks to Nishant Agarwala for reporting the issue. CVE-2016-6893 (LP: #1614841) New Features - For header_filter_rules matching, RFC 2047 encoded headers, non-encoded headers and header_filter_rules patterns are now all decoded to unicode. Both XML character references of the form &#nnnn; and unicode escapes of the form \Uxxxx in patterns are converted to unicodes as well. Both headers and patterns are normalized to 'NFKC' normal form before matching, but the normalization form can be set via a new NORMALIZE_FORM mm_cfg setting. Also, the web UI has been updated to encode characters in text fields that are invalid in the character set of the page's language as XML character references instead of '?'. This should help with entering header_filter_rules patterns to match 'odd' characters. This feature is experimental and is problematic for some cases where it is desired to have a header_filter_rules pattern with characters not in the character set of the list's preferred language. For patterns without such characters, the only change in behavior should be because of unicode normalization which should improve matching. For other situations such as trying to match a Subject: with CJK characters (range U+4E00..U+9FFF) on an English language (ascii) list, one can enter a pattern like '^subject:.*[一-鿿]' or '^subject:.*[\u4e00;-\u9fff;]' to match a Subject with any character in the range, and it will work, but depending on the actual characters and the browser, submitting another, even unrelated change can garble the original entry although this usually occurs only with ascii pages and characters in the range \u0080-\u00ff. The \Uxxxx unicode escapes must have exactly 4 hex digits, but they are case insensitive. (LP: #558155) - Thanks to Jim Popovitch REMOVE_DKIM_HEADERS can now be set to 3 to preserve the original headers as X-Mailman-Original-... before removing them. - Several additional templates have been added to those that can be edited via the web admin GUI. (LP: #1583387) - SMTPDirect.py can now do SASL authentication and STARTTLS security when connecting to the outgoiung MTA. Associated with this are new Defaults.py/mm_cfg.py settings SMTP_AUTH, SMTP_USER, SMTP_PASSWD and SMTP_USE_TLS. (LP: #558281) - There is a new Defaults.py/mm_cfg.py setting SMTPLIB_DEBUG_LEVEL which can be set to 1 to enable verbose smtplib debugging to Mailman's error log to help with debugging 'low level smtp failures'. (LP: #1573074) - A list's nonmember_rejection_notice attribute will now be the default rejection reason for a held non-member post in addition to it's prior role as the reson for an automatically rejected non-member post. (LP: #1572330) i18n - The French translation of 'Dutch' is changed from 'Hollandais' to 'Néerlandais' per Francis Jorissen. - Some German language templates that were incorrectly utf-8 encoded have been recoded as iso-8859-1. (LP: #1602779) - Japanese translation and documentation in messages/ja has been updated by Yasuhito FUTATSUKI. Bug fixes and other patches - The admin Membership List letter links could be incorrectly rendered as Unicode strings following a search. (LP: #1604544) - We no longer throw an uncaught TypeError with certain defective crafted POST requests to Mailman's CGIs. (LP: #1602608) - Scrubber links in archives are now in the list's preferred_language rather than the poster's language. (LP: #1586505) - Improved logging of banned subscription and address change attempts. (LP: #1582856) - In rare circumstances a list can be removed while the admin or listinfo CGI or bin/list_lists is running causing an uncaught MMUnknownListError to be thrown. The exception is now caught and handled. (LP: #1582532) - Set the Date: header in the wrapper message when from_is_list or dmarc_moderation_action is Wrap Message. (LP: #1581215) - A site can now set DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL to None or the null string if it wants to avoid using this. (LP: #1578450) - The white space to the left of the admindb Logout link is no longer part of the link. (LP: #1573623) 2.1.22 (17-Apr-2016) i18n - Fixed a typo in the German options.html template. (LP: #1562408) - An error in the Brazilian Portugese translation of Quarterly has been fixed thanks to Kleber A. Benatti. - The Brazilian Portugese translation has been updated by Emerson Ribeiro de Mello. Bug fixes and other patches - All addresses in data/virtual-mailman are now properly appended with VIRTUAL_MAILMAN_LOCAL_DOMAIN and duplicates are not generated if the site list is in a virtual domain. (LP: #1570630) - DMARC mitigations will now find the From: domain to the right of the rightmost '@' rather than the leftmost '@'. (LP: #1568445) - DMARC mitigations for a sub-domain of an organizational domain will now use the organizational domain's sp= policy if any. (LP: #1568398) - Modified NewsRunner.py to ensure that messages gated to Usenet have a non-blank Subject: header and when munging the Message-ID to add the original to References: to help with threading. (LP: #557955) - Fixed the pipermail archiver to do a better job of figuring the date of a post when its Date: header is missing, unparseable or has an obviously out of range date. This should only affect bin/arch as ArchRunner has code to fix dates at least if ARCHIVER_CLOBBER_DATE_POLICY has not been set to 0 in mm_cfg.py. If posts have been added in the past to a list's archive using bin/arch and an imported mbox, running bin/arch again could result is some of those posts being archived with a different date. (LP: #1555798) - Fixed an issue with CommandRunner shunting a malformed message with a null byte in the body. (LP: #1553888) - Don't collapse multipart with a single sub-part inside multipart/signed parts. (LP: #1551075) 2.1.21 (28-Feb-2016) New Features - There is a new dmarc_none_moderation_action list setting and a DEFAULT_DMARC_NONE_MODERATION_ACTION mm_cfg.py setting to optionally apply Munge From or Wrap Message actions to posts From: domains that publish DMARC p=none. The intent is to eliminate failure reports to the domain owner for messages that would be munged or wrapped if the domain published a stronger DMARC policy. See the descriptions in Defaults.py, the web UI and the bug report for more. (LP: #1539384) - Thanks to Jim Popovitch there is now a feature to automatically turn on moderation for a malicious list member who attempts to flood a list with spam. See the details for the Privacy options ... -> Sender filters -> member_verbosity_threshold and member_verbosity_interval settings in the web admin UI and the documentation in Defaults.py for the DEFAULT_MEMBER_VERBOSITY_* and VERBOSE_CLEAN_LIMIT settings for information. - bin/list_members now has options to display all moderated or all non-moderated members. - There is now a mm_cfg.py setting GLOBAL_BAN_LIST which is like the individual list's ban_list but applies globally to all subscribe requests. See the description in Defaults.py for more details. i18n - The Japanese translation has been updated by Yasuhito FUTATSUKI. - Also thanks to Miloslav Trmac and Yasuhito FUTATSUKI, the l10n for Mailman's bin/ commands has been fixed to display using the character set of the user's work station even when Mailman's character set for the language is different. Because this has not been tested over a wide set of locales, there is an mm_cfg.py switch DISABLE_COMMAND_LOCALE_CSET to disable it if it causes problems. (LP: #558167) - The Polish translation has been updated by Stefan Plewako. - The German translation has been updated by Mirian Margiani and Bernhard Schmidt. - The Russian translation has been updated by Danil Smirnov. - Several Galician templates that were improperly encoded as iso-8859-1 have been fixed. (LP: #1532504) - The Brazilian Portugese translation has been updated by Emerson Ribeiro de Mello. Bug fixes and other patches - If DMARC lookup fails to find a policy, also try the Organizational Domain. Associated with this is a new mm_cfg.py setting DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL which sets the URL used to retrieve the data for the algorithm that computes the Organizational Domain. See https://publicsuffix.org/list/ for info. (LP: #1549420) - Modified contrib/mmdsr to correctly report No such list names that contain ". - User's "Acknowledge" option will now be honored for posts to anonymous lists. (LP: #1546679) - Fixed a typo in the Non-digest options regular_exclude_ignore description thanks to Yasuhito FUTATSUKI. - DEFAULT_PASS_MIME_TYPES has been changed to accept text/plain sub-parts from message/rfc822 parts and multipart parts other than mixed and alternative and also accept pgp signatures. This only applies to newly created lists and other than pgp signatures, still only accepts text/plain. (LP: #1517446) - Modified contrib/mmdsr to report held and banned subscriptions and DMARC lookups in their own categories. - Fixed a bug that could create a garbled From: header with certain DMARC mitigation actions. (LP: #1536816) - Treat a poster's address which matches an equivalent_domains address as a list member for the regular_exclude_ignore check. (LP: #1526550) - Fixed an issue that sometimes left no white space following subject_prefix. (LP: #1525954) - Vette log entries for banned subscriptions now include the source of the request if available. (LP: #1525733) - Submitting the user options form for a user who was asynchronously unsubscribed would throw an uncaught NotAMemberError. (LP: #1523273) - It was possible under some circumstances for a message to be shunted after a handler rejected or discarded it, and the handler would be skipped upon unshunting and the message accepted. (LP: #1519062) - Posts gated to usenet will no longer have other than the target group in the Newsgroups: header. (LP: #1512866) - Invalid regexps in *_these_nonmembers, subscribe_auto_approval and ban_list are now logged. (LP: #1507241) - Refactored the GetPattern list method to simplify extending @listname syntax to new attributes in the future. Changed Moderate.py to use the GetPattern method to process the *_these_nonmembers lists. - Changed CookHeaders to default to using space rather than tab as continuation_ws when folding headers. (LP: #1505878) - Fixed the 'pidfile' path in the sample init.d script. (LP: #1503422) - Subject prefixing could fail to collapse multiple 'Re:' in an incomming message if they all came after the list's subject_prefix. This is now fixed. (LP: #1496620) - Defended against a user submitting URLs with query fragments or POST data containing multiple occurrences of the same variable. (LP: #1496632) - Fixed bin/mailmanctl to check its effective rather than real uid. (LP: #1491187) - Fixed cron/gate_news to catch EOFError on opening the newsgroup. (LP: #1486263) - Fixed a bug where a delayed probe bounce can throw an AttributeError. (LP: #1482940) - If a list is not digestable an the user is not currently set to receive digests, the digest options will not be shown on the user's options page. (LP: #1476298) - Improved identification of remote clients for logging and subscribe form checking in cases where access is via a proxy server. Thanks to Jim Popovitch. Also updated contrib/mmdsr for log change. - Fixed an issue with shunted messages on a list where the charset for the list's preferred_language had been changed from iso-8859-1 to utf-8 without recoding the list's description. (LP: #1462755) - Mailman-Postfix integration will now add mailman@domain entries in data/virtual-mailman for each domain in POSTFIX_STYLE_VIRTUAL_DOMAINS which is a host_name of a list. This is so the addresses which are exposed on admin and listinfo overview pages of virtual domains will be deliverable. (LP: #1459236) - The vette log entry for DMARC policy hits now contains the list name. (LP: #1450826) - If SUBSCRIBE_FORM_SECRET is enabled and a user's network has a load balancer or similar in use the POSTing IP might not exactly match the GETting IP. This is now accounted for by not requiring the last octet (16 bits for ipV6) to match. (LP: #1447445) - DKIM-Signature:, DomainKey-Signature: and Authentication-Results: headers are now removed by default from posts to anonymous lists. (LP: #1444673) - The list admin web UI Mambership List search function often doesn't return correct results for search strings (regexps) that contain non-ascii characters. This is partially fixed. (LP: #1442298) 2.1.20 (31-Mar-2015) Security - A path traversal vulnerability has been discovered and fixed. This vulnerability is only exploitable by a local user on a Mailman server where the suggested Exim transport, the Postfix postfix_to_mailman.py transport or some other programmatic MTA delivery not using aliases is employed. CVE-2015-2775 (LP: #1437145) New Features - There is a new Address Change sub-section in the web admin Membership Management section to allow a list admin to change a list member's address in one step rather than adding the new address, copying settings and deleting the old address. (LP: #266809) i18n - The Russian translation has been updated by Danil Smirnov. - The Polish translation has been updated by Stefan Plewako. Bug fixes and other patches - A LookupError in SpamDetect on a message with RFC 2047 encoded headers in an unknown character set is fixed. (LP: #1427389) - Fixed a bug in CommandRunner that could process the second word of a body line as a command word and a case sensitivity in commands in Subject: with an Re: prefix. (LP: #1426829) - Fixed a bug in CommandRunner that threw an uncaught KeyError if the input to the list-request address contained a command word terminated by a period. (LP: #1426825) 2.2 Branch Backports (released in conjunction with 2.1.19) The following New Features and Bug Fixes have been in an "unofficial, never to be released" Mailman 2.2 branch for several years. Until now, they were never implemented on the official 2.1 branch because of their i18n impacts. Given that there have been a number of i18n impacting changes due to DMARC mitigations in the last few releases, it has been decided to backport these as well. All of these changes have been running in production on several lists for years without problems other than untranslated strings, so they should be reasonably "bug free". New Features - There is a new list attribute 'subscribe_auto_approval' which is a list of email addresses and regular expressions matching email addresses whose subscriptions are exempt from admin approval. (LP: #266609) - Confirmed member change of address is logged in the 'subscribe' log, and if admin_notify_mchanges is true, a notice is sent to the list owner using a new adminaddrchgack.txt template. - Added an 'automate' option to bin/newlist to send the notice to the admin without the prompt. - The processing of Topics regular expressions has changed. Previously the Topics regexp was compiled in verbose mode but not documented as such which caused some confusion. Also, the documentation indicated that topic keywords could be entered one per line, but these entries were not handled properly. Topics regexps are now compiled in non-verbose mode and multi-line entries are 'ored'. Existing Topics regexps will be converted when the list is updated so they will continue to work. - Added real name display to the web roster. (LP: #266754) Bug fixes and other patches - Changed the response to an invalid confirmation to be more generic. Not all confirmations are subscription requests. - Changed the default nonmember_rejection_notice to be more user friendly. (LP: #418728) - Added "If you are a list member" qualification to some messages from the options login page. (LP: #266442) - Changed the 'Approve' wording in the admindbdetails.html template to 'Accept/Approve' for better agreement with the button labels. - Added '(by thread)' to the previous and next message links in the archive to emphasize that even if you got to the message from a subject, date or author index, previous and next are still by thread. 2.1.19 (28-Feb-2015) New Features - The subscribe_auto_approval feature backported from the 2.2 branch and described above has been enhanced to accept entries of the form @listname to auto approve members of another list. (LP: #1417093) - There is a new list attribute dmarc_wrapped_message_text and a DEFAULT_DMARC_WRAPPED_MESSAGE_TEXT setting to set the default for new lists. This text is added to a message which is wrapped because of dmarc_moderation_action in a separate text/plain part that precedes the message/rfc822 part containing the original message. It can be used to provide an explanation of why the message was wrapped or similar info. - There is a new list attribute equivalent_domains and a DEFAULT_EQUIVALENT_DOMAINS setting to set the default for new lists which in turn defaults to the empty string. This provides a way to specify one or more groups of domains, e.g., mac.com, me.com, icloud.com, which are considered equivalent for validating list membership for posting and moderation purposes. - There is a new WEB_HEAD_ADD setting to specify text to be added to the section of Mailman's internally generated web pages. This doesn't apply to pages built from templates, but in those cases, custom templates can be created. (LP: #1409396) - There is a new DEFAULT_SUBSCRIBE_OR_INVITE setting. Set this to Yes to make the default selection on the admin Mass Subscriptions page Invite rather than Subscribe. (LP: #1404511) - There is a new list attribute in the Bounce processing section. bounce_notify_owner_on_bounce_increment if set to Yes will cause Mailman to notify the list owner on every bounce that increments a list member's score but doesn't result in a probe or disable. There is a new configuration setting setting DEFAULT_BOUNCE_NOTIFY_OWNER_ON_BOUNCE_INCREMENT to set the default for new lists. This in turn defaults to No. (LP: #1382150) Changed behavior - Mailman's log files, request.pck files and heldmsg-* files are no longer created world readable to protect against access by untrusted local users. Note that permissions on existing log files won't be changed so if you are concerned about this and don't rotate logs or have a logrotate process that creates new log files instead of letting Mailman create them, you will need to address that. (LP: #1327404) Other changes - The Python Powered logo image has been replaced in the misc/ directory in the source distribution. Depending on how you've installed these images, you may need to copy PythonPowered.png from the misc/ directory in the source or from the $prefix/icons/ installed directory to another location for your web server. (LP: #1408575) i18n - The Polish translation has been updated by Stefan Plewako. - The Interlingua translation has been updated by Martijn Dekker. - The Japanese message catalog has been updated by SATOH Fumiyasu. - Mailman's character set for Romanian has been changed from iso-8859-2 to utf-8 and the templates and messages recoded. This change will require running 'bin/arch --wipe' on any existing Romanian language lists in order to recode the list's archives, and will require recoding any edited templates in lists/LISTNAME/ro/*, templates/DOMAIN/ro/* and templates/site/ro/*. It may also require recoding any existing iso-8859-2 text in list attributes. (LP: #1418735) - Mailman's character set for Russian has been changed from koi8-r to utf-8 and the templates and messages recoded. This change will require running 'bin/arch --wipe' on any existing Russian language lists in order to recode the list's archives, and will require recoding any edited templates in lists/LISTNAME/ru/*, templates/DOMAIN/ru/* and templates/site/ru/*. It may also require recoding any existing koi8-r text in list attributes. (LP: #1418448) - Mailman's versions.py has been augmented to help with the above two character set changes. The first time a list with preferred_language of Romanian or Russian is accessed or upon upgrade to this release, any list attributes which have string values such as description, info, welcome_msg, etc. that appear to be in the old character set will be converted to utf-8. This is done recursively for the values (but not the keys) of dictionary attributes and the elements of list and tuple attributes. - The Russian message catalog and templates have been further updated by Danil Smirnov. - The Romanian message catalog has been updated. (LP: #1415489) - The Russian templates have been updated by Danil Smirnov. (LP: #1403462) - The Japanese translation has been updated by SATOH Fumiyasu. (LP: #1402989) - A minor change in the French translation of a listinfo subscribe form message has been made. (LP: #1331194) Bug fixes and other patches - Because of privacy concerns with the 2.2 backport adding real name to list rosters, this is controlled by a new ROSTER_DISPLAY_REALNAME setting that defaults to No. You may wish to set this to Yes in mm_cfg.py. - Organization: headers are now unconditionally removed from posts to anonymous lists. Regexps in ANONYMOUS_LIST_KEEP_HEADERS weren't kept if the regexp included the trailing ':'. This is fixed too. (LP: #1419132) - The admindb interface has been fixed so the the detail message body display doesn't lose part of a multi-byte character, and characters which are invalid in the message's charset are replaced rather than the whole body not being converted to the display charset. (LP: #1415406) - Fixed a bug in bin/rmlist that would throw an exception or just fail to remove held message files for a list with regexp special characters in its name. (LP: #1414864) - When applying DMARC mitigations, CookHeaders now adds the original From: to Cc: rather than Reply-To: in some cases to make MUA 'reply' and 'reply all' more consistent with the non-DMARC cases. (LP: #1407098) - The Subject: of the list welcome message wasn't always in the user's preferred language. Fixed. (LP: #1400988) - Accept email command in Subject: prefixed with Re: or similar with no intervening space. (LP: #1400200) - Fixed a UnicodeDecodeError that could occur in the web admin interface if 'text' valued attributes have unicode values. (LP: #1397170) - We now catch the NotAMemberError exception thrown if an authenticated unsubscribe is submitted from the user options page for a nonmember. (LP: #1390653) - Fixed an archiving bug that would cause messages with 'Subject: Re:' only to be indexed in the archives without a link to the message. (LP: #1388614) - The vette log entry for a message discarded by a handler now includes the list name and the name of the handler. (LP: #558096) - The options CGI now rejects all but HTTP GET and POST requests. (LP: #1372199) - A list's poster password will now be accepted on an Urgent: header. (LP: #1371678) - Fixed a bug which caused a setting of 2 for REMOVE_DKIM_HEADERS to be ignored. (LP: #1363278) - Renamed messages/sr/readme.sr to README.sr. (LP: #1360616) - Moved the dmarc_moderation_action checks from the Moderate handler to the SpamDetect handler so that the Reject and Discard actions will be done before the message might be held by header_filter_rules, and the Wrap Message and Munge From actions will be done on messages held by header_filter_rules if the message is approved. (LP: #1334450) -