Mailman-Developers February 2002

mailman-developers@python.org

46 participants
73 discussions

Re: [Mailman-Developers] Mailman password and administrative reminders
by Dan Mick 14 Aug '03

14 Aug '03

? This very message came to me with the following header: Errors-To: mailman-developers-admin(a)python.org All my bounces come to the list admin address, set in the admin webpage, in the second field of General Options. Do you have that set to something, and bounces still come to root? > 2. Bounces are sent to the poor postmaster instead of a -admin address. > I'm not entirely certain, but I think an Errors-To: header or something > like that in all Mailman messages might allow one to distribute that load > somewhat.

8 11

External subscriber lists in 2.1
by J C Lawrence 23 Aug '02

23 Aug '02

Barry, In 2.1 when used with external subscriber storage (eg SQL), will the new equivalent of qrunner request and load the entire subscriber DB onto the heap prior to broadcast? <<Yeah, I'm cheating and being lazy on not checking the source myself>> Reason: This poses scaling problems for lists with very large numbers of subscribers. I'd suggest paging thru the set in blocks. ObExcuse: Chap on -users asking about millions of subscribers. -- 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.

3 4

Interesting study -- spam on posted addresses...
by Chuq Von Rospach 05 Jun '02

05 Jun '02

Interesting article on slashdot: <http://slashdot.org/article.pl?sid=02/02/17/2031249> Basically, DSLreports did a test, and found that e-mail addresses posted on a web site could start seeing spam in as little as 8 hours. I mention it for two reasons. One, since mail lists manage e-mail addresses (and archives of e-mail addresses), it is yet antother indication of just why we have to be careful about presenting and disclosing that stuff. And second, since one of the addresses presented and disclosed is that of the admin, we really need to come up with ways that allow newbies to contact an admin without easily disclosing addresses to spammers. And, unfortunately, the security problems with formmail.pl have shown THAT isn't really the answer... Chuq -- Chuq Von Rospach (chuqui(a)plaidworks.com -- http://www.chuqui.com/) Will Geek for hardware. Very funny, Scotty. Now beam my clothes down here, will you?

20 125

Problem in checkdbs
by Rodolfo Pilas 27 Mar '02

27 Mar '02

I am receving the following notice from my server. (I use Python 2.0 and MM 2.1a3) Can you tell me how to fix it? (thank you) -----Mensaje reenviado----- From: Cron Daemon <root(a)segurux.com> To: mailman(a)segurux.com Subject: Cron <mailman@guru> /usr/bin/python /usr/lib/mailman/cron/checkdbs Date: 14 Jan 2002 12:00:02 -0500 Traceback (most recent call last): File "/usr/lib/mailman/cron/checkdbs", line 104, in ? main() File "/usr/lib/mailman/cron/checkdbs", line 67, in main text = text + '\n' + pending_requests(mlist) File "/usr/lib/mailman/cron/checkdbs", line 82, in pending_requests when, addr, passwd, digest, lang = mlist.GetRecord(id) ValueError: unpack tuple of wrong size

2 1

[ANNOUNCE] Mailman 2.1 alpha 2
by barry＠digicool.com 25 Mar '02

25 Mar '02

This the official announcement for Mailman 2.1 alpha 2. Because it's an alpha, this announcement is only going out to the mailman-* mailing lists. I'll make two warnings: you probably should still not use this version for production systems (but TIA for any and all testing you do with it!), and I've already had a couple of bug fixes from early adopters. 2.1a2 should still be useful, but you might want to keep an eye on cvs and the mailman-checkins list for updates. I am only making the tarball available on SourceForge, so you'll need to go to http://sf.net/projects/mailman to grab it. You'll also need to upgrade to mimelib-0.4, so be sure to go to http://sf.net/projects/mimelib to grab and install that tarball first. To view the on-line documentation, see http://www.list.org/MM21/index.html or http://mailman.sf.net/MM21/index.html Below is an excerpt from the NEWS file for all the changes since 2.1alpha1. There are a bunch of new features coming down the pike, and I hope to have an alpha3 out soon. I'm also planning on doing much more stress testing of this version with real list traffic, and I'm hoping we'll start to get more languages integrated into cvs. Enjoy, -Barry -------------------- snip snip -------------------- 2.1 alpha 2 (11-Jul-2001) - Building o mimelib 0.4 is now required. Get it from http://mimelib.sf.net. If you've installed an earlier version of mimelib, you must upgrade. o /usr/local/mailman is now the default installation directory. Use configure's --prefix switch to change it back to the default (/home/mailman) or any other installation directory of your choice. - Security o Better definition of authentication domains. The following roles have been defined: user, list-admin, list-moderator, creator, site-admin. o There is now a separate role of "list moderator", which has access to the pending requests (admindb) page, but not the list configuration pages. o Subscription confirmations can now be performed via email or via URL. When a subscription is received, a unique (sha) confirm URL is generated in the confirmation message. Simply visiting this URL completes the subscription process. o In a similar manner, removal requests (via web or email command) no longer require the password. If the correct password is given, the removal is performed immediately. If no password is given, then a confirmation message is generated. - Internationalization o More I18N patches. The basic infrastructure should now be working correctly. Spanish templates and catalogs are included, and English, French, Hungarian, and Big5 templates are included. o Cascading specializations and internationalization of templates. Templates are now search for in the following order: list-specific location, domain-specific location, site-wide location, global defaults. Each search location is further qualified by the language being displayed. This means that you only need to change the templates that are different from the global defaults. Templates renamed: admlogin.txt => admlogin.html Templates added: private.html - Web UI o Redesigned the user options page. It now sits behind an authentication so user options cannot be viewed without the proper password. The other advantage is that the user's password need not be entered on the options page to unsubscribe or change option values. The login screen also provides for password mail-back, and unsubscription w/ confirmation. Other new features accessible from the user options page include: ability to change email address (with confirmation) both per-list and globally for all list on virtual domain; global membership password changing; global mail delivery disable/enable; ability to suppress password reminders both per-list and globally; logout button. [Note: the handle_opts cgi has gone away] o Color schemes for non-template based web pages can be defined via mm_cfg. o Redesign of the membership management page. The page is now split into three subcategories (Membership List, Mass Subscription, and Mass Removal). The Membership List subcategory now supports searching for member addresses by regular expression, and if necessary, it groups member addresses first alphabetically, and then by chunks. Mass Subscription and Mass Removal now support file upload, with one address per line. o Hyperlinks from the logos in the footers have been removed. The sponsors got too much "unsubscribe me!" spam from desperate user of Mailman at other sites. o New buttons on the digest admin page to send a digest immediately (if it's non-empty), to start a new digest volume with the next digest, and to select the interval with which to automatically start a new digest volume (yearly, monthly, quarterly, weekly, daily). DEFAULT_DIGEST_VOLUME_FREQUENCY is a new configuration variable, initially set to give a new digest volume monthly. o Through-the-web list creation and removal, using a separate site-wide authentication role called the "list creator and destroyer" or simply "list creator". If the configuration variable OWNERS_CAN_DELETE_THEIR_OWN_LISTS is set to 1 (by default, it's 0), then list admins can delete their own lists. This feature requires an adaptor for the particular MTA you're using. An adaptor for Postfix is included, as is a dumb adaptor that just emails mailman@yoursite with the necessary Sendmail style /etc/alias file changes. Some MTAs like Exim can be configured to automatically recognize new lists. The adaptor is selected via the MTA option in mm_cfg.py - Email UI o In email commands, "join" is a synonym for "subscribe". "remove" and "leave" are synonyms for "unsubscribe". New robot addresses are support to make subscribing and unsubscribing much easier: mylist-join@mysite mylist-leave@mysite o Confirmation messages have a shortened Subject: header, containing just the word "confirm" and the confirmation cookie. This should help for MUAs that like to wrap long Subject: lines, messing up confirmation. o Mailman now recognizes an Urgent: header, which, if it contains the list moderator or list administrator password, forces the message to be delivered immediately to all members (i.e. both regular and digest members). The message is also placed in the digest. If the password is incorrect, the message will be bounced back to the sender. - Performance o Refinements to the new qrunner subsystem which preserves FIFO order of messages. o The qrunner is no longer started from cron. It is started by a Un*x init-style script called bin/mailmanctl (see below). cron/qrunner has been removed. - Command line scripts o bin/mailmanctl script added, which is used to start, stop, and restart the qrunner daemon. o bin/qrunner script added which allows a single sub-qrunner to run once through its processing loop. o bin/change_pw script added (eases mass changing of list passwords). o bin/update grows a -f switch to force an update. o bin/newlang renamed to bin/addlang; bin/rmlang removed. o bin/mmsitepass has grown a -c option to set the list creator's password. The site-wide `create' web page is linked to from the admin overview page. o bin/newlist's -o option is removed. This script also grows a way of spelling the creation of a list in a specific virtual domain. o The `auto' script has been removed. o bin/dumpdb has grown -m/--marshal and -p/--pickle options. o bin/list_admins can be used to print the owners of a mailing list. o bin/genaliases regenerates from scratch the aliases and aliases.db file for the Postfix MTA. - Archiver o New archiver date clobbering option, which allows dates to only be clobber if they are outrageously out-of-date (default setting is 15 days on either side of received timestamp). New configuration variables: ARCHIVER_CLOBBER_DATE_POLICY ARCHIVER_ALLOWABLE_SANE_DATE_SKEW The archived copy of messages grows an X-List-Received-Date: header indicating the time the message was received by Mailman. o PRIVATE_ARCHIVE_URL configuration variable is removed (this can be calculated on the fly, and removing it actually makes site configuration easier). - Miscellaneous o Several new README's have been added. o Most syslog entries for the qrunner have been redirected to logs/error. o On SIGHUP, qrunner will re-open all its log files and restart all child processes. See "bin/mailmanctl restart". - Patches and bug fixes o SF patches and bug fixes applied: 420396, 424389, 227694, 426002, 401372 (partial), 401452. o Fixes in 2.0.5 ported forward: Fix a lock stagnation problem that can result when the user hits the `stop' button on their browser during a write operation that can take a long time (e.g. hitting the membership management admin page). o Fixes in 2.0.4 ported forward: Python 2.1 compatibility release. There were a few questionable constructs and uses of deprecated modules that caused annoying warnings when used with Python 2.1. This release quiets those warnings. o Fixes in 2.0.3 ported forward: Bug fix release. There was a small typo in 2.0.2 in ListAdmin.py for approving an already subscribed member (thanks Thomas!). Also, an update to the OpenWall security workaround (contrib/securelinux_fix.py) was included. Thanks to Marc Merlin.

17 38

more snapshot woes...
by Ron Jarrell 12 Mar '02

12 Mar '02

I love playing catchup after a long hiatus :-)... Seems like somethings out of sync here... While doing the make install, update appears to blow chunks, because of PortableUnixMailbox.. Compiling /home/mailman/Mailman/aliases.py ... Compiling /home/mailman/Mailman/htmlformat.py ... Compiling /home/mailman/Mailman/i18n.py ... Listing /home/mailman/Mailman/pythonlib ... Compiling /home/mailman/Mailman/versions.py ... Traceback (most recent call last): File "bin/update", line 47, in ? from Mailman import MailList File "/home/mailman/Mailman/MailList.py", line 49, in ? from Mailman.Archiver import Archiver File "/home/mailman/Mailman/Archiver/__init__.py", line 17, in ? from Archiver import * File "/home/mailman/Mailman/Archiver/Archiver.py", line 32, in ? from Mailman import Mailbox File "/home/mailman/Mailman/Mailbox.py", line 40, in ? class Mailbox(mailbox.PortableUnixMailbox): AttributeError: PortableUnixMailbox *** Error code 1 make: Fatal error: Command failed for target `update' 55.0u 111.0s 3:17 84% 0+0k 0+0io 0pf+0w

5 13

Database version updates drop nomail settings
by Les Niles 12 Mar '02

12 Mar '02

There's a small bug in 2.1alpha4 in updating a list's database to the DATA_FILE_VERSION, causing "nomail" settings to not be propagated forward: MailList.CheckVersion() reloads the database, taking care to make sure that the reload doesn't trigger a recursive call to CheckVersion(). But if the list wasn't locked, CheckVersion() then calls Lock(), and Lock() calls Load() again, this time generating a recursive call to CheckVersion(). This recursion is only one deep because now the list is locked, but even that is too much for versions.CanonicalizeUserOptions() since it clears the old-style "nomail" flag after setting the delivery status in the new database. Here's a patch that fixes this. -les --------------------------------------------------------------------- *** MailList.py.orig Sun Jan 6 23:04:01 2002 --- MailList.py Sat Feb 9 22:42:36 2002 *************** *** 146,157 **** # # Lock management # ! def Lock(self, timeout=0): self.__lock.lock(timeout) # Must reload our database for consistency. Watch out for lists that # don't exist. try: ! self.Load() except Exception: self.Unlock() raise --- 146,157 ---- # # Lock management # ! def Lock(self, timeout=0, check_version=1): self.__lock.lock(timeout) # Must reload our database for consistency. Watch out for lists that # don't exist. try: ! self.Load(check_version) except Exception: self.Unlock() raise *************** *** 557,563 **** # We must hold the list lock in order to update the schema waslocked = self.Locked() if not waslocked: ! self.Lock() try: from versions import Update Update(self, stored_state) --- 558,564 ---- # We must hold the list lock in order to update the schema waslocked = self.Locked() if not waslocked: ! self.Lock(check_version=0) try: from versions import Update Update(self, stored_state)

3 4

a problem in upgrading with moderated lists
by Fil 11 Mar '02

11 Mar '02

Hi, when you upgrade Mailman to 2.1a3 from 2.0, moderated lists correctly take on the attributes generic_nonmember_action = Hold default_member_moderation = Yes However the latter is valid only for NEW subscribers. Subscribers already registered have their moderation bit set to 0 (not moderated) whereas it should be set to 1 (moderated) to conform to the previous settings. And, by the way, these settings are not given through config_list -o -- Fil

2 1

Problem while upgrade to mailman 2.1 alpha
by Dan Ohnesorg 09 Mar '02

09 Mar '02

I am also triing to upgrade to never version and I have this troubles: Upgrading from version 0x20005f0 to 0x20100a4 getting rid of old source files fixing all the perms on your old html archives to work with b6 If your archives are big, this could take a minute or two... hotovo Updating mailing list: test - updating old private mbox file looks like you have a really recent CVS installation... you're either one brave soul, or you already ran me - updating old public mbox file looks like you have a really recent CVS installation... you're either one brave soul, or you already ran me Fixing language templates: test Updating mailing list: kecy Traceback (most recent call last): File "./update", line 531, in ? errors = main() File "./update", line 413, in main errors = errors + dolist(listname) File "./update", line 183, in dolist mlist = MailList.MailList(listname, lock=0) File "../Mailman/MailList.py", line 101, in __init__ self.Load() File "../Mailman/MailList.py", line 543, in Load self.CheckVersion(dict) File "../Mailman/MailList.py", line 560, in CheckVersion self.Lock() File "../Mailman/MailList.py", line 154, in Lock self.Load() File "../Mailman/MailList.py", line 543, in Load self.CheckVersion(dict) File "../Mailman/MailList.py", line 563, in CheckVersion Update(self, stored_state) File "../Mailman/versions.py", line 53, in Update CanonicalizeUserOptions(l) File "../Mailman/versions.py", line 339, in CanonicalizeUserOptions if l.getMemberOption(k, mm_cfg.DisableDelivery): File "../Mailman/OldStyleMemberships.py", line 120, in getMemberOption self.__assertIsMember(member) File "../Mailman/OldStyleMemberships.py", line 113, in __assertIsMember raise Errors.NotAMemberError, member Mailman.Errors.NotAMemberError: fickman(a)atlas.cz and it is alo true, that this user is listed only in section 'user_options': { '3zsmost(a)schoolnet.cz': 8, 'fickman(a)atlas.cz': 8, of dump_db. Sure, the database is corrupt, but it is not fatal, i think the upgrage should run OK. cheers dan -- ________________________________________ DDDDDD DD DD Dan Ohnesorg, supervisor on POWER DD OOOO Dan(a)feld.cvut.cz DD OODDOO Dep. of Power Engineering DDDDDD OO CTU FEL Prague, Bohemia OO OO work: +420 2 24352785;+420 2 24972109 OOOO home: +420 311 679679;+420 311 679311 ________________________________________ Nezlob se na růži, že má trny; raduj se, že tak trnitý keř má růže. -- Arabské přísloví

2 1

Re: [Mailman-Developers] gate_news still broken in 2.1b..
by Ron Jarrell 28 Feb '02

28 Feb '02

At 03:03 PM 2/26/02 -0500, Barry A. Warsaw wrote: >>>>>> "RJ" == Ron Jarrell <jarrell(a)vt.edu> writes: > > RJ> Yea, you know, I sat down last night when I got home and > RJ> looked at the code, and slapped myself on the forehead with > RJ> the same realization, that I was blaming the wrong piece of > RJ> code... > > RJ> As for the patch - BING! We have a winner. > >Awesome. Thanks, I'm going to commit this change. Cool.. How much more you going to do before the formal beta release? Enough seems to be working (and I have enough of a handle on things I might have to handwave) that I'm tempted to start putting it up on my production box... But if there's going to be a last minute flurry of features and fixes before then, I probably won't bother. Oh, BTW, simple typo in the admin pages. In the VARHELP=topics/topics_enabled, the sentence: "The body of the message can also be optionally scanned for Subject: and Keyword: headers" Keyword: should be "Keywords:", which bit me for a while, because, of course, *that* was the occurrence of the word (which is right two other places in the paragraph) that I focused on. Although, I'm thinking, either Keyword: or Keywords: out to to work. Especically since it'll usually be one keyword...

2 1

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

Mailman-Developers February 2002