I put together a tarball for Mailman 2.1.6 beta 2 and placed on my
Japanese Mailman site at:
This 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:
- 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 of
making it easier to run withlist scripts that live in $prefix/bin.
- bin/newlist grew two new options: -u/--urlhost and -e/--emailhost
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,
than the old 'mylist@hostname' syntax (which is still supported for
backward compatibility, but deprecated).
- Added the ability for Mailman generated passwords (both member and
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.
generated by Mailman are now 8 characters by default for members,
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 neither
is supported yet.
- Python 2.4 compatibility issue: time.strftime() became strict
'day of year' range. (1078482)
- New feature: automatic discards of held messages. List owners
set how many days to hold the messages in the moderator request
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:
subject", if mm_cfg.OLD_STYLE_PREFIXING is set No. The default style
is "Re: [list-name]" if numbering is not set, for backward
If the list owner is using numbering feature by "%d" directive,
style, "[list-name 123] Re:", is always used.
- List owners can now use Scrubber to get the attachments scrubbed
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
- Filter attachments by filename extensions. (1027882)
- Bugs and patches: 955381 (older Python compatibility),
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
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
I received this message and tested German confirmation mail at my test
site but no trouble. The confirmaiton message had iso-8859-1 charset
declared properly and no error within mailman. Has anyone experienced
-------- Original Message --------
Subject: German template files for 2.1.6
Date: Thu, 20 Jan 2005 16:57:51 +0100
From: Christian Schoepplein <chris(a)schoeppi.net>
To: Tokio Kikuchi <tkikuchi(a)is.kochi-u.ac.jp>
I noticed a problem with the German template files under mailman 2.1.5.
If a user wants to change his mailaddress globaly for several lists, he
gets a mail witch he must send back for confirmation. In this mail,
witch is generated from a template, are special german letters (ü, ö,
etc.). Mailman has problems with this special letters, the confirmation
does not work. Changing the mailaddress globaly via the webinterface
works witout problems.
I changed the templates for my 2.1.5 installation and the special German
letters are substituted. No every thing works fine.
However, it would be nice to have this new German templates in 2.1.6
too. I can change this templates and send them to you for integration
in the final 2.1.6 release, if you can tell me, where I can download
the latest 2.1.6 tar.gz archive. I haven't found anything on the mailman
homepage or on sourceforge and my knowletge of cvs is very small so I
can't use the cvs to get the latest release :-(.
Thank you and best regards,
Christian Schoepplein <chris at schoeppi.net>
Windows -> REBOOT ... Linux -> BE ROOT
Linux fuer Blinde: http://www.blinux.suse.de
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
Alexander Shopov wrote:
> What is the preferred encoding for the translations?
> I cannot possibly write everything in ASCII - we employ the Cyrillic
> I would very much like to use UTF-8 because it is widely supported and
> it is native to the HTML docs.
There is no problem because Serbian and Ukrainian already use utf-8.
add_language('ru', _('Russian'), 'koi8-r')
add_language('sr', _('Serbian'), 'utf-8')
add_language('uk', _('Ukrainian'), 'utf-8')
By the way, Bulgarian language locale is 'bg' right?
> Will you need formal copyright assignment? I will assign the copyright
> in the translation to the FSF but do you need a formal written paper?
> Should it be signed by a local public notary?
Well, I have not done yet. (Barry, should I?)
> If possible - can you give a more specific date for the release. I am
> starting the translation this weekend and I would really appreciate it
> if it makes it in the next release.
It highly depends on the schedule of Barry the leading developer ;-).
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
I am Alexander Shopov and I am the committer of the Bulgarian Gnome
I would like to start (and finish) Bulgarian translation of mailman.
Browsing through the archives of this list revealed that I should read
this document first: README-I18n.en
After I make my translation - what is the preferred way to commit it?
I can send it here, to some of the maintainers or if needed I can commit
directly to CVS.
If possible - can you give me some release date for the next release so
that I know the time frame for finishing the translation.
I am a college student of china. i found that the chinese support of
Mailman is quite out of date, so i want to be the volunteer to finish
the task. any advice? thanks!
Invent and fit; have fits and reinvent!
We toast the Lisp programmer who pens his thoughts within nests of
The last update of the message catalog is broken and it needs to be redone.
It seems there were several versions of the new reset_pw command in the tree
used so the catalog now have entries for both reset_pw and reset_pw.~1~.
On Fri, 2005-01-07 at 23:23, Tokio Kikuchi wrote:
> > Should I try to build this and push it out to the web sites?
> > -Barry
> Well, we may need a japanized latex to compile ps/pdf versions.
> Actually, I've put up a web version on my site.
> and I now working on
Which I'm sure I don't have, unless my Gentoo version of latex can be
coerced into building with Japanese support.
The alternatives are for you to check the Japanese versions into
admin/www yourself so that I can push them out to the web sites, or for
us to simply add links to your site from the main site(s).
I'm cc'ing mailman-i18n because this offer goes for anyone else who
wants to maintain language-specific versions of the manuals. I'm happy
either way -- we can maintain it in the Mailman CVS or link to your
I had a user send me the following corrections for the invite.txt in es
The first instatance of mensaje (in first paragraph) is spelled: mensjae
Throughout both of the following corrections are also needed.
solo should be : sólo
dirijido should be: dirigido
Mind you I do not speak Spanish, so I'm taking their word for it. If this has already been corrected sorry to bother you.
American Friends Service Committee