Mailman 3 January 2005 - Mailman-Developers

Mailman 2.1.6 beta 2 released
by Tokio Kikuchi 27 Jan '05

27 Jan '05

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.tgz 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: 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 of sys.path, making it easier to run withlist scripts that live in $prefix/bin. - bin/newlist grew two new options: -u/--urlhost and -e/--emailhost which 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 and list 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 neither language is supported yet. - Python 2.4 compatibility issue: time.strftime() became strict about 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/

8 12

Re: [Mailman-Developers] Mailman 2.1.6 beta 2 released
by J C Lawrence 27 Jan '05

27 Jan '05

On Tue, 25 Jan 2005 23:03:51 -0800 Alan Batie <alan(a)batie.org> wrote: > 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?)... I do all of my documentation, letters, book writing, articles etc in LaTeX. Tis may not be statistically significant. > ... but I still want to simply be able to "tar xzvf" then "less > INSTALL" whatever I'm installing. Do note that LaTeX and TeX is a plain text format and is quite human readable, even more so than say [nrt]roff. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

2 1

Re: [Mailman-Developers] [Fwd: Re: [Mailman-Announce] Mailman 2.1.6 beta 1]
by Tokio Kikuchi 26 Jan '05

26 Jan '05

Niels Bakker wrote: > Hello, > >> http://www.jwz.org/doc/threading.html > > Mailman 2.1.6b1 breaks this algorithm, specifically this step: > > | Only two things need to be done with the subject strings: ask whether > | they begin with `Re:', and compare the non-Re parts for equivalence. > | So you can get away with interning or otherwise hashing these, too. > > ... by moving the tag to the front, which makes the Subject not start > with "Re: " anymore (or, more precisely, Mutt's $reply_regexp variable). OK, it's not pipermail problem but MUA's. Pipermail never rely ambiguous "Re:" threading. (That was why I was always annoyed by "no subject" or "question" message threaded under very old messages in my Netscape 7.) > Therefore, please back out this change. I think I can add some code before the 2.1.6 final release to exchage Re: and prefix order for the subject prefix without numbering. (Yes, we now have a nice feature to add numbering in the subject prefix.) -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/

4 6

Re: [Mailman-Developers] [Fwd: Re: [Mailman-Announce] Mailman 2.1.6 beta 1]
by Tokio Kikuchi 24 Jan '05

24 Jan '05

Niels Bakker wrote: > > Can the default be kept the same as current behaviour? It helps with > threading by Mutt, in the absence of In-Reply-To (e.g. all mails sent > with most Outlook, MS Exchange MUAs). > Oh, Yes, I will. >>First post: >> Subject: [prefix 1] testing >>Second posted: >> Subject: Re: [prefix 1] testing >>Second delivered from mailman: >> Subject: [prefix 2] Re: testing >>Third posted: >> Subject: Re: [prefix 2] Re: tesing >>Third delivered: >> Subject: [prefix 3] Re: testing > > > You can do an in-place replacement, you do not necessarily need to bring > it forward in the Subject: line, do you? > There is also a history on this side older than mailman. ;-) -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/

1 0

changeMemberAddress() preserving neither nomail nor topics
by Jim Tittsler 23 Jan '05

23 Jan '05

"pointer-gaim" mentioned on IRC that bin/clone_member was not copying the nomail flag to the newly cloned member. It looks like OldStyleMemberships's changeMemberAddress() was preserving neither nomail (now that simply copying the user's flags is not enough) nor any topics the original member was subscribed to. I've submitted a patch for one way that can be fixed. <http://sourceforge.net/tracker/index.php? func=detail&aid=1107631&group_id=103&atid=300103> -- Jim Tittsler http://www.OnJapan.net/ GPG: 0x01159DB6 Python Starship http://Starship.Python.net/ Ringo MUG Tokyo http://www.ringo.net/rss.html

1 0

Your pending subscription request to mailman-developers - more info needed, please reply ASAP
by JC Dill 22 Jan '05

22 Jan '05

Hello, We have set the mailman-developers list to require list admin approval for membership requests because of a recent problem with some people subscribing to this list and then posting messages that belong elsewhere. Can you please share with us your background with mailman and your purpose for subscribing to the developers list so we can approve your membership request? Thanks! This is our second request. If we don't get a response from you within 4 days your subscription request will be rejected. jc

1 1

Your pending subscription request to mailman-developers - more info needed, please reply ASAP (second request)
by JC Dill 22 Jan '05

22 Jan '05

Hello, We have set the mailman-developers list to require list admin approval for membership requests because of a recent problem with some people subscribing to this list and then posting messages that belong elsewhere. Can you please share with us your background with mailman and your purpose for subscribing to the developers list so we can approve your membership request? Thanks! This is our second request. If we don't get a response from you within 4 days your subscription request will be rejected. jc

1 0

Postfix.py extension for virtual_domain management
by Mike Gabriel 22 Jan '05

22 Jan '05

hi there, i have newly subscribed to the list as i want to propose an alternative (extended) postfix MTA backend. i called it PostfixVirtual.py as a working title. it enables an extended support for postfix virtual domains. all this can also be achieved by manually adding some aliases in postfix's /etc/aliases manually, but why not manage all of the following automagically: 1. ================================= enable one and the same list on all configured virtual domains (e.g. gurus@...) create a list: "all_virtualdomains.gurus" this will lead to an alias stanza in the virtual-mailman map: # STANZA START: all_virtualdomains.gurus # CREATED: Fri Jan 21 22:00:02 2005 gurus(a)dom1.com all_virtualdomains.gurus gurus(a)dom2.com all_virtualdomains.gurus gurus(a)dom3.org all_virtualdomains.gurus gurus-admin(a)dom1.com all_virtualdomains.gurus-admin gurus-admin(a)dom2.com all_virtualdomains.gurus-admin gurus-admin(a)dom3.org all_virtualdomains.gurus-admin gurus-bounces(a)dom1.com all_virtualdomains.gurus-bounces gurus-bounces(a)dom2.com all_virtualdomains.gurus-bounces gurus-bounces(a)dom3.org all_virtualdomains.gurus-bounces gurus-confirm(a)dom1.com all_virtualdomains.gurus-confirm gurus-confirm(a)dom2.com all_virtualdomains.gurus-confirm gurus-confirm(a)dom3.org all_virtualdomains.gurus-confirm gurus-join(a)dom1.com all_virtualdomains.gurus-join gurus-join(a)dom2.com all_virtualdomains.gurus-join gurus-join(a)dom3.org all_virtualdomains.gurus-join gurus-leave(a)dom1.com all_virtualdomains.gurus-leave gurus-leave(a)dom2.com all_virtualdomains.gurus-leave gurus-leave(a)dom3.org all_virtualdomains.gurus-leave gurus-owner(a)dom1.com all_virtualdomains.gurus-owner gurus-owner(a)dom2.com all_virtualdomains.gurus-owner gurus-owner(a)dom3.org all_virtualdomains.gurus-owner gurus-request(a)dom1.com all_virtualdomains.gurus-request gurus-request(a)dom2.com all_virtualdomains.gurus-request gurus-request(a)dom3.org all_virtualdomains.gurus-request gurus-subscribe(a)dom1.com all_virtualdomains.gurus-subscribe gurus-subscribe(a)dom2.com all_virtualdomains.gurus-subscribe gurus-subscribe(a)dom3.org all_virtualdomains.gurus-subscribe gurus-unsubscribe(a)dom1.com all_virtualdomains.gurus-unsubscribe gurus-unsubscribe(a)dom2.com all_virtualdomains.gurus-unsubscribe gurus-unsubscribe(a)dom3.org all_virtualdomains.gurus-unsubscribe all_virtualdomains.gurus(a)dom1.com all_virtualdomains.gurus all_virtualdomains.gurus-admin(a)dom1.com all_virtualdomains.gurus-admin all_virtualdomains.gurus-bounces(a)dom1.com all_virtualdomains.gurus-bounces all_virtualdomains.gurus-confirm(a)dom1.com all_virtualdomains.gurus-confirm all_virtualdomains.gurus-join(a)dom1.com all_virtualdomains.gurus-join all_virtualdomains.gurus-leave(a)dom1.com all_virtualdomains.gurus-leave all_virtualdomains.gurus-owner(a)dom1.com all_virtualdomains.gurus-owner all_virtualdomains.gurus-request(a)dom1.com all_virtualdomains.gurus-request all_virtualdomains.gurus-subscribe(a)dom1.com all_virtualdomains.gurus-subscribe all_virtualdomains.gurus-unsubscribe(a)dom1.com all_virtualdomains.gurus-unsubscribe # STANZA END: all_virtualdomains.gurus only thing that has to be done to the list is add "gurus" to acceptable_aliases() 2. ================================= enable very common listnames like members@..., people@..., etc. on more than one domain, addressing different mailing lists on the same host. on my server i host two different aikido dojos that have different groups of members. what i did is create two lists: org.aikido1.members(a)aikido1.org org.aikido2.members(a)aikido2.org only if the front part of the listname matches the virtual_domain (in a backward fashion) then the list is treated in a special manner by PostfixVirtual.py: # STANZA START: org.aikido1.members # CREATED: Fri Jan 21 22:00:02 2005 members(a)aikido1.org org.aikido1.members members-admin(a)aikido1.org org.aikido1.members-admin members-bounces(a)aikido1.org org.aikido1.members-bounces members-confirm(a)aikido1.org org.aikido1.members-confirm members-join(a)aikido1.org org.aikido1.members-join members-leave(a)aikido1.org org.aikido1.members-leave members-owner(a)aikido1.org org.aikido1.members-owner members-request(a)aikido1.org org.aikido1.members-request members-subscribe(a)aikido1.org org.aikido1.members-subscribe members-unsubscribe(a)aikido1.org org.aikido1.members-unsubscribe org.aikido1.members(a)aikido1.org org.aikido1.members org.aikido1.members-admin(a)aikido1.org org.aikido1.members-admin org.aikido1.members-bounces(a)aikido1.org org.aikido1.members-bounces org.aikido1.members-confirm(a)aikido1.org org.aikido1.members-confirm org.aikido1.members-join(a)aikido1.org org.aikido1.members-join org.aikido1.members-leave(a)aikido1.org org.aikido1.members-leave org.aikido1.members-owner(a)aikido1.org org.aikido1.members-owner org.aikido1.members-request(a)aikido1.org org.aikido1.members-request org.aikido1.members-subscribe(a)aikido1.org org.aikido1.members-subscribe org.aikido1.members-unsubscribe(a)aikido1.org org.aikido1.members-unsubscribe # STANZA END: org.aikido1.members again, you have to add the alias in acceptable_aliases() ("members(a)aikido1.org") i am not sure, if this kind of functionality might be interesting to you. i find it quite handy and appreciate it in my very own special mailman setup. the PostfixVirtual.py code (orginally taken from Postfix.py in mailman 2.1.5 (Debian Sarge)) can be downloaded from here: http://www.ecology.uni-kiel.de/~mgabriel/downloads/PostfixVirtual.py looking forward to any resonance, mike gabriel -- network administration, ecology centre, kiel university, germany Mike Gabriel, olshausenstr 75, 24118 kiel, germany fon-work: +49 431 880-1186 fon-home: +49 431 6474196 mail: mgabriel(a)ecology.uni-kiel.de www: http://www.ecology.uni-kiel.de, http://zope.ecology.uni-kiel.de

1 1

What would send to bare administrator
by John W. Baxter 22 Jan '05

22 Jan '05

OK, that subject might hit a filter somewhere. ;-) Mark Shapiro wrote in another thread, in mailman-users: If you haven't changed SMTP_LOG_EACH_FAILURE in mm_cfg.py, the 3 failures should be logged in Mailman's smtp-failure log. Which prompted me to look there, and find Jan 18 14:47:56 2005 (20931) delivery to administrator failed with code 501: <administrator>: recipient address must contain a domain That's true, the way the MTA (Exim) is configured. A quick grep in the source didn't reveal a case where Mailman attempts to send mail to the unqualified recipient <administrator>. Does anyone happen to know where it is? When I get back (from the doctor) I'll try to find out what was going on Tuesday around that time. --John

2 2

Re: [Mailman-Developers] [Fwd: Re: [Mailman-Announce] Mailman 2.1.6 beta 1]
by Tokio Kikuchi 21 Jan '05

21 Jan '05

>>I think I can add some code before the 2.1.6 final release to exchage >>Re: and prefix order for the subject prefix without numbering. (Yes, we >>now have a nice feature to add numbering in the subject prefix.) > > > Or avoid messing with the Subject in the first place if the tag is > already there? Sounds like the easier way out to me... Like I said, I want to get rid of prefix far away from the start of the subject. Anyway, I wanted fix another small bug that Re: is MIME encoded. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/

2 2