Mailman 3 March 2002 - Mailman-Developers

Mailman 2.1b1
by Kory Wheatley March 28, 2002

March 28, 2002

Where's the documentation that goes in detail about all the new and changed features for Mailman 2.1b1. -- ######################################### Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him.

2 1

new BounceRunner
by Fil March 27, 2002

March 27, 2002

While the recent commits for BounceRunner seem to be working fine in terms of memory and CPU, I'm suddenly seing many files in the qfiles/bad/ directory. These files seem to be legitimate bounces (ie the usual postfix-format bounce message). -- Fil

2 1

clean install of mailman-2.1a4
by Kory Wheatley March 27, 2002

March 27, 2002

I did a clean install of mailman-2.1a4 and the web interface is working fine, but I'm having problems with sending messages. I'm running Red Hat 7.2 with Python 2.2 and sendmail 8.11. My aliases for the list I created are correct. I changed the symbolic link in /etc/smrsh to point to mailman rather than wrapper. Here is the following error, I hope I can get some feedback on the solution to the problem. Mar 14 15:38:46 2002 (15583) Uncaught runner exception: please run connect() first Mar 14 15:38:46 2002 (15583) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 104, in __oneloop self.__onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 152, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/OutgoingRunner.py", line 61, in _dispose func(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/SMTPDirect.py", line 101, in process conn.quit() File "/var/tmp/python2-2.2-root/usr/lib/python2.2/smtplib.py", line 671, in quit self.docmd("quit") File "/var/tmp/python2-2.2-root/usr/lib/python2.2/smtplib.py", line 352, in docmd self.putcmd(cmd,args) File "/var/tmp/python2-2.2-root/usr/lib/python2.2/smtplib.py", line 308, in putcmd self.send(str) File "/var/tmp/python2-2.2-root/usr/lib/python2.2/smtplib.py", line 300, in send raise SMTPServerDisconnected('please run connect() first') SMTPServerDisconnected: please run connect() first Mar 14 15:52:54 2002 (15583) Uncaught runner exception: please run connect() first Mar 14 15:52:54 2002 (15583) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 104, in __oneloop self.__onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 152, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/OutgoingRunner.py", line 61, in _dispose func(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/SMTPDirect.py", line 101, in process conn.quit() File "/var/tmp/python2-2.2-root/usr/lib/python2.2/smtplib.py", line 671, in quit self.docmd("quit") File "/var/tmp/python2-2.2-root/usr/lib/python2.2/smtplib.py", line 352, in docmd self.putcmd(cmd,args) File "/var/tmp/python2-2.2-root/usr/lib/python2.2/smtplib.py", line 308, in putcmd self.send(str) File "/var/tmp/python2-2.2-root/usr/lib/python2.2/smtplib.py", line 300, in send raise SMTPServerDisconnected('please run connect() first') SMTPServerDisconnected: please run connect() first -- ######################################### Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him.

2 1

unshunt error
by Ron Jarrell March 27, 2002

March 27, 2002

/home/mailman/bin/unshunt * Traceback (most recent call last): File "/home/mailman/bin/unshunt", line 76, in ? main() File "/home/mailman/bin/unshunt", line 64, in main usage(1) File "/home/mailman/bin/unshunt", line 42, in usage print >> sys.stderr, _(__doc__) NameError: global name '_' is not defined

3 2

Re: [Mailman-Developers] Re: message is unparsable and lost data files for filebase
by Dan Mick March 27, 2002

March 27, 2002

> >>>>> "tm" == totschnig michael <totschnig.michael(a)uqam.ca> writes: > > tm> But by comparing with the MTA's log file, I could understand > tm> that the message in question has probably been spam. Is there > tm> another place where mailman could have put it for inspection, > tm> or do I have to change the configuration to keep track of such > tm> problems? > > Dan's right, but you need to enable saving of bad messages by setting > QRUNNER_SAVE_BAD_MESSAGES = 1 in your mm_cfg.py file. Bad messages > aren't saved by default. > > This is almost always going to be caused by malformed MIME messages, > which are (almost?) always spam. I wouldn't worry about them. Depressingly, about half of mine are misformatted bounce messages. Apparently people just can't keep their damned fingers off bounce messages.

2 1

Problem in checkdbs
by Rodolfo Pilas March 27, 2002

March 27, 2002

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

Misc thoughs on 2.0.5ish to 2.1b1
by Ron Jarrell March 26, 2002

March 26, 2002

Upgrading my production server... I'm amazed I didn't notice some of this stuff on my test server, although that might be the fact that this big a jump has side effects that regular cvs updates didn't, (since update didn't necessarily do some things if I let it run before it knew how to do something, I suspect), or maybe the fact that my test lists are basically *me* in a variety of configurations, or maybe I'm just suddenly hitting bugs.. The upgrade process really ought not fill the errors log during the update process with "database for list whatever is corrupt, falling back to (whatever)"... Was the site password supposed to die? I can't remember if that happened to me during the various cvs upgrades I've done. The site password, once fixed, no longer works the same way when used as a trump password. For instance, *just* using the site password (and any old string under "email address") could get me into archives, listinfo screens, subscriber lists, etc. Now it seems I have to explicitly know an address that's subscribed to the list to use the sitepass - which is particularly annoying when I'm testing a new list that doesn't *have* subscribers on it! I'd rather the test be "(valid address and pass) OR site pass" not "valid address and (valid pass or site pass)" like it used to be... ***THE UPGRADE REALLY OUGHT NOT PUT IN THE "There are not messages in the archive" HOLDER URL FOR LISTS THAT *HAVE* THINGS IN THE ARCHIVE ALREADY!!** The above scared the (#($*# out of me... Having now had to use a list that had more than 2 test users on it, I agree with the comments made earlier - the new alphabetical subdivision system is a royal pain. I'm getting just 4-5 users at a time, and have to click as many as 28 times to quickly scan my users to see, for instance, who's in nomail, whereas before it was at most 4-5 chunks. Allowing an optional "just show me a chunk worth" is *well* worth it for convenience sake. Or just let the regexp display show them by chunks.. (I was really hoping that it would, but no, it just broke them down by alphabet when it got to be too many again...) For "new" flags, like "nodupes", when converting users, shouldn't we apply the current default user flag mask? With the default 256, no old users will have nodupes set, but all new users will... I'm sure I'll think of more :-)

1 0

a bug? the latest CVS (2.1b1)
by Mentor Cana March 25, 2002

March 25, 2002

The "Emergency moderation of all list traffic" check-box does not stay checked beyond the current session. If you "Logout" and login back that the check-box is uncheck and the red-color disappears. -- Mentor

3 2

[ANNOUNCE] Mailman 2.1 alpha 2
by barry＠digicool.com March 25, 2002

March 25, 2002

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

Are digests broken in mailman 2.1b1?
by Marc MERLIN March 25, 2002

March 25, 2002

[resending with correct From:] On my live/test system, mailman has been sending empty digests since last friday (when I upgraded to 2.1a4++ and later b1) Is this just me? What I get is exactly: ---------------------------------------------------------------------------- From: svlug-request(a)svlug.org Subject: svlug Digest, Vol 28, Issue 2 To: svlug(a)svlug.org X-BeenThere: svlug(a)lists.svlug.org X-Mailman-Version: 2.1b1 Precedence: bulk List-Help: <mailto:svlug-request@lists.svlug.org?subject=help> List-Post: <mailto:svlug@lists.svlug.org> List-Subscribe: <http://lists.svlug.org/lists/listinfo/svlug>, <mailto:svlug-request@lists.svlug.org?subject=subscribe> List-Id: discussion list for the Silicon Valley Linux Users Group. <svlug.lists.svlug.org> List-Unsubscribe: <http://lists.svlug.org/lists/listinfo/svlug>, <mailto:svlug-request@lists.svlug.org?subject=unsubscribe> List-Archive: http://lists.svlug.org/archives/svlug/ Content-Type: multipart/mixed; boundary="===============9383223389590416=="; charset="en" Content-Transfer-Encoding: base64 Sender: svlug-bounces+marc=merlins.org(a)svlug.org Errors-To: svlug-bounces+marc=merlins.org(a)lists.svlug.org Message-Id: <E16nmGE-0005Jv-00(a)mail.svlug.org> Date: Wed, 20 Mar 2002 12:00:38 -0800 X-Spam-Status: No, hits=0.6 required=8.0 tests=NO_REAL_NAME version=2.11 Content-Length: 11689 Lines: 337 ---------------------------------------------------------------------------- The mail stops here, there is no body whatsoever. It's not just me, I only subscribed as digest because my users told me it was broken. Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f(a)merlins.org for PGP key

2 3