Mailman 2.1.6 beta 2 released
Hi,
I put together a tarball for Mailman 2.1.6 beta 2 and placed on my Japanese Mailman site at:
http://mm.tkikuchi.net/mailman-2.1.6b2.tgzThis is the second beta release of 2.1.6 which are roughly scheduled to be released by the end of February. Please grab it from above site and upgrade your mailman.
Change from 2.1.6b1 are mainly subject prefix problems for Mutt (and other?) users and translation catalog template (pot) also.
Here is excerpt from NEWS file:
2.1.6 (XX-XXX-200X)
- Most of the installation instructions have been moved to a latex
document. See admin/www/mailman-install/index.html for details.
- VERP_PROBES is disabled by default.
- bin/withlist can be run without a list name, but only if -i is given.
Also, withlist puts the directory it's found in at the end ofsys.path, making it easier to run withlist scripts that live in $prefix/bin.
- bin/newlist grew two new options: -u/--urlhost and -e/--emailhostwhich lets the user provide the web and email hostnames for the new mailing list. This is a better way to specify the domain for the list, rather than the old 'mylist@hostname' syntax (which is still supported for backward compatibility, but deprecated).
- Added the ability for Mailman generated passwords (both member andlist admin) to be more cryptographically secure. See new configuration variables USER_FRIENDLY_PASSWORDS, MEMBER_PASSWORD_LENGTH, and ADMIN_PASSWORD_LENGTH. Also added a new bin/withlist script called reset_pw.py which can be used to reset all member passwords. Passwords generated by Mailman are now 8 characters by default for members, and 10 characters for list administrators.
- Allow editing of the welcome message from the admin page (1085501).
- A potential cross-site scripting hole in the driver script has been
closed. Thanks to Florian Weimer for its discovery. Also, turn
STEALTH_MODE on by default.
- Chinese languages moved from 'big5' and 'gb' to 'zh_TW' and 'zh_CN'
respectively for compliance to the IANA spec. Note that neitherlanguage is supported yet.
- Python 2.4 compatibility issue: time.strftime() became strictabout the 'day of year' range. (1078482)
- New feature: automatic discards of held messages. List owners can now set how many days to hold the messages in the moderator request queue. cron/checkdb will automatically discard old messages. (790494)
- Improved mail address sanity check. (1030228)
- SpamDetect.py now checks attachment header. (1026977)
- New feature: subject_prefix can be configured to include a sequence
number which is taken from the post_id variable. Also, the prefix is
always put at the start of the subject, i.e. "[list-name] Re: original subject", if mm_cfg.OLD_STYLE_PREFIXING is set No. The default style is "Re: [list-name]" if numbering is not set, for backward compatibility. If the list owner is using numbering feature by "%d" directive, the new style, "[list-name 123] Re:", is always used.
- List owners can now use Scrubber to get the attachments scrubbed (held in the web archive), if the site admin permits it in mm_cfg.py. New variables introduced are SCRUBBER_DONT_USE_ATTACHMENT_FILENAME and SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION in Defaults.py for scrubber behavior. (904850)
- Filter attachments by filename extensions. (1027882)
- Bugs and patches: 955381 (older Python compatibility),1020102/1013079/ 1020013 (fix spam filter removed), 665569 (newer Postfix bounce detection), 970383 (moderator -1 admin requests pending), 873035 (subject handling in -request mail), 799166/946554 (makefile compatibility), 872068 (add header/footer via unicode), 1032434 (KNOWN_SPAMMERS check for multi-header), 1025372 (empty Cc:), 789015 (fix pipermail URL), 948152 (Out of date link on Docs), 1099138 (Scrubber.py breaks on None part), 1099840/1099840 (deprecated % insertion), 880073/933762 (List-ID RFC compliance), 1090439 (passwd reminder shunted),
-- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/
Tokio Kikuchi wrote:
- Most of the installation instructions have been moved to a latex document. See admin/www/mailman-install/index.html for details.
This is *not* a positive move. Installation instructions should be in a flat text document, unless you're installing it from a web browser or word processor. I install most software from a shell, and want to be able to see what I'm doing without having to install the instructions on a web server somewhere, or copying them over to my workstation where the web browser can get at them locally, or installing lynx so I can read them when less is easier to move around with.
On Tuesday 25 January 2005 22:32, Alan Batie wrote:
This is *not* a positive move.
I 100% agree. Since Mailman is designed to be installed from the shell (and certain commands run from the shell) and since a web / mail server likely is not going to have a GUI installed on it, the docs should be in plain text.
Cheers
-- CODEgrunt slave@codegrunt.com / http://codegrunt.com
Alan Batie wrote:
I install most software from a shell, and want to be able to see what I'm doing without having to install the instructions on a web server somewhere
I will take this back *slightly* in the case of mailman: since it's designed to work with a webserver, you're obviously installing it where the docs are actually viewable (at least if they're html, does anyone actually use latex anymore?), but I still want to simply be able to "tar xzvf" then "less INSTALL" whatever I'm installing.
Alan Batie wrote:
Tokio Kikuchi wrote:
- Most of the installation instructions have been moved to a latex document. See admin/www/mailman-install/index.html for details.This is *not* a positive move. Installation instructions should be in a flat text document, unless you're installing it from a web browser or word processor. I install most software from a shell, and want to be able to see what I'm doing without having to install the instructions on a web server somewhere, or copying them over to my workstation where the web browser can get at them locally, or installing lynx so I can read them when less is easier to move around with.
OK, we should add like this: '(Or, the plain text version, admin/www/mailman-install.txt.)'
Others may be convenient pointing their browsers at: http://www.list.org/mailman-install/index.html
-- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/
"Alan" == Alan Batie <alan@batie.org> writes:
Alan> Tokio Kikuchi wrote:
>> - Most of the installation instructions have been moved to a
>> latex document. See admin/www/mailman-install/index.html for
>> details.
Alan> This is *not* a positive move. Installation instructions
Alan> should be in a flat text documentI have to agree. Doesn't it make more sense to move to something like reStructuredText if you need to produce somewhat nice-looking web or printed documents without much effort?
-- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.
I third the motion. I hate it when the docs for something are in something other than plain text. I rarely am logged in with a gui - always a terminal mode, and even html can get goofy.
Bob
---------- Original Message ----------- From: "Stephen J. Turnbull" <stephen@xemacs.org> To: Alan Batie <alan@batie.org> Cc: mailman-developers@python.org Sent: Wed, 26 Jan 2005 20:39:01 +0900 Subject: Re: [Mailman-Developers] Mailman 2.1.6 beta 2 released
"Alan" == Alan Batie <alan@batie.org> writes:
Alan> Tokio Kikuchi wrote: >> - Most of the installation instructions have been moved to a >> latex document. See admin/www/mailman-install/index.html for >> details. Alan> This is *not* a positive move. Installation instructions Alan> should be in a flat text documentI have to agree. Doesn't it make more sense to move to something like reStructuredText if you need to produce somewhat nice-looking web or printed documents without much effort?
-- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305- 8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.
Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/bob%40nleaudio.com ------- End of Original Message -------
--On January 26, 2005 08:36:55 -0500 Bob Puff <bob@nleaudio.com> wrote:
I third the motion. I hate it when the docs for something are in something other than plain text. I rarely am logged in with a gui - always a terminal mode, and even html can get goofy.
Bob
I fourth it. I don't even know if I have anything that can read latex format documents. Well, I guess I probably do, but I don't want to go digging it out all the time. My preferences are for plain text and perhaps MAN pages with the distribution, and HTML on the web.
-- Ian Eiloart Servers Team Sussex University ITS
Hi,
Before some one 'fifth' this, I should say: The plain text version mailman-install is already in the tar ball -- admin/www/mailman-install.txt. What is missing is the pointer.
Ian Eiloart wrote:
--On January 26, 2005 08:36:55 -0500 Bob Puff <bob@nleaudio.com> wrote:
I third the motion. I hate it when the docs for something are in something other than plain text. I rarely am logged in with a gui - always a terminal mode, and even html can get goofy.
Bob
I fourth it. I don't even know if I have anything that can read latex format documents. Well, I guess I probably do, but I don't want to go digging it out all the time. My preferences are for plain text and perhaps MAN pages with the distribution, and HTML on the web.
-- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/
On Wed, 2005-01-26 at 06:39, Stephen J. Turnbull wrote:
I have to agree. Doesn't it make more sense to move to something like reStructuredText if you need to produce somewhat nice-looking web or printed documents without much effort?
I think the doc source doesn't make much of a difference, and I like the mkhowto scripts that come with Python. They can easily take latex and produce HTML, PDF, and plaintext. I don't think the reST tools are quite there yet.
-Barry
On Jan 26, 2005, at 11:10 AM, Barry Warsaw wrote:
On Wed, 2005-01-26 at 06:39, Stephen J. Turnbull wrote:
I have to agree. Doesn't it make more sense to move to something like reStructuredText if you need to produce somewhat nice-looking web or printed documents without much effort?
I think the doc source doesn't make much of a difference, and I like the mkhowto scripts that come with Python. They can easily take latex and produce HTML, PDF, and plaintext. I don't think the reST tools are quite there yet.
As probably one of few people here who's spent any time using the mkhowto scripts, I'm with Barry. They're pretty decent, make fairly nice output in several different formats, and are easily available to people who already have python set up. AND I think since we already have a decent chunk of documentation in this formats, it makes sense to keep our documentation in this format rather than having a mess of other tools about.
Related: I get mail from people who've printed out the mailman documents, so the more nicely formatted stuff is getting used... and appreciated!
As long as the plan is to have some nice plaintext documents in the root when we do the actual release, this seems good to me.
Terri
PS - Tokio: I've got a pile of patches for the in-line documentation of the stuff in bin/ that I need to double-check and submit. Will there be any problem if I check them in now? I can wait if it makes your life easier.
PS - Tokio: I've got a pile of patches for the in-line documentation of the stuff in bin/ that I need to double-check and submit. Will there be any problem if I check them in now? I can wait if it makes your life easier.
No problem! Thanks.
-- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/
On Wed, 2005-01-26 at 01:32, Alan Batie wrote:
Tokio Kikuchi wrote:
- Most of the installation instructions have been moved to a latex document. See admin/www/mailman-install/index.html for details.This is *not* a positive move. Installation instructions should be in a flat text document, unless you're installing it from a web browser or word processor. I install most software from a shell, and want to be able to see what I'm doing without having to install the instructions on a web server somewhere, or copying them over to my workstation where the web browser can get at them locally, or installing lynx so I can read them when less is easier to move around with.
Don't fret, for the final release we'll include a PDF and a plain text version of the installation documentation. But this re-org is way better than the scads of READMEs.
-Barry
participants (8)
-
Alan Batie -
Barry Warsaw -
Bob Puff -
Ian Eiloart -
Ron Brogden -
Stephen J. Turnbull -
Terri Oda -
Tokio Kikuchi