In a prior round of email, Ken mentioned that we would need to key the
mail list entries to something other than the person's actual email
address in order to implement the flexible user information editing
capability of the web (changing one's sendto address, etc.). I agree
that this is needed, sooner or later. Since I haven't seen the code yet,
how difficult is it to just make a unique key for each subscriber and
key the database off that with address as just one value?
I hope I'm not using …
[View More]this list too soon.
--
Robin K. Friedrich Houston, Texas
Python Professional Services, Inc.
friedrich(a)pythonpros.com
http://www.pythonpros.com
[View Less]
For anyone that's interested, i've packaged up my current version of
mailman as three files in
ftp://www.python.org/pub/python/contrib/Networking/mailman
(Note that the klm.p1 patches *supercede* any prior patch packages i
sent out - lots of developments today and yesterday. I will try to
stick with incremental patches for incremental releases from this
point forward.)
mailman-1.0b1.tar.gz - The most recent surviving version (since his
server crash and data loss) of john viegas mailman …
[View More]distribution that i
could find, and
klm.p1 - patches i've assembled over three or four days of hacking, to
bring the revision to 1.0b1.1 (from 1.0b1). They implement a bunch of
features, some of which i found imperative. There's a synopsis of the
new features in...
klm.notes1 - notes about the first set of patches. Here's the major
highlights:
- optional anti-spam filter, imposing the constraint that postings
with the 'require_explicit_destination' option set must have the
name of the list among the explicit recipients ('to' or 'cc') addrs
in the message. This measure has been working *quite* nicely on the
majordomo lists that i hacked it onto.
- rmlist now does *not* get nasty and delete all the lists,
templates, and archive hierarchies if you invoke it without any
arguments. !
- All the list configuration defaults are collected in
modules/mm_cfg.py, so ideally the installer compiles the wrappers,
puts the files in place, and then applies their settings to this
file to configure all the defaults for all the lists.
- monthly password reminders are sent out collecting together each
users passwords in a single message, rather than sending a message
per password.
- Prevent cascading subject-line list prefix (which effect many of
you on the meta-sig may have noticed in the initial postings -
i hadn't tried using the subject-line prefix in my test lists!-)
There's more - read klm.notes1 for details. And these fixes are
really not so big compared to the very nice features mailman offers in
the first place. I won't go into that here, just suggest you try it
out if you're looking for a good maillist mechanism...
Note that i'll be away most of tomorrow and this weekend (in the grand
python tradition of being unreachable just after a release). Barring
any catastrophic behaviors of the setup in my absence, i'll probably
be announcing this on the python newsgroup early next week, and
switching over the rest of the python.org mailing lists at that point.
(I will probably work with andrew kuchling to integrate with the newer
pipermail, first.)
Ken Manheimer klm(a)python.org 703 620-8990 x268
(orporation for National Research |nitiatives
# If you appreciate Python, consider joining the PSA! #
# <http://www.python.org/psa/>. #
[View Less]
This is what ends up as the header in the 1999-August.txt file
>From CJSB06A(a)prodigy.com Wed, 9 Apr 1997 00:55:56, -0500
Date: Wed, 9 Apr 1997 00:55:56, -0500
From: MR LARRY N REED CJSB06A(a)prodigy.com
Subject: Jarrell Plantation, Jones county Ga
This is what you get when it dies...
Updating index files for archive [1999-August]
Date
Subject
Author
Thread
Computing threaded index
Traceback (innermost last):
File "/home/mailman/bin/arch", line 47, in ?
archiver.close()
…
[View More] File "/home/mailman/Mailman/Archiver/HyperArch.py", line 906, in close
self.update_dirty_archives()# Update all changed archives
File "/home/mailman/Mailman/Archiver/HyperArch.py", line 871, in update_dirty_archives
self.update_archive(i)
File "/home/mailman/Mailman/Archiver/pipermail.py", line 330, in update_archive
self.write_index_header()
File "/home/mailman/Mailman/Archiver/HyperArch.py", line 738, in write_index_header
self.updateThreadedIndex()
File "/home/mailman/Mailman/Archiver/pipermail.py", line 269, in updateThreadedIndex
self.database.setThreadKey(self.archive, article.threadKey+'\000'+article.msgid, msgid)
File "/home/mailman/Mailman/Archiver/HyperDatabase.py", line 256, in setThreadKey
self.threadIndex[key]=msgid
File "/home/mailman/Mailman/Archiver/HyperDatabase.py", line 144, in __setitem__
self.current_index = self.sorted.index(current_item)
ValueError: list.index(x): x not in list
I'm suspecting, from looking at it for a while (wish I actually knew
python... although thanks to mailman, I'm starting to learn) that
the problem is buried in rfc822.py's parsedate_tz routine; it's
confused by the comma. I see where it checks to see if that last
character of the tm field is a , and tried to delete it, but either
it's not working, or I'm barking up the wrong branch of the right
tree; because getting rid of that comma makes things work again...
[View Less]