Sorry about the busted references, I'm on the digest.
"ben" == Ben Gertzfield che@debian.org writes
ben> On a massive list (Mailman 2.0.6) I run that regularly gets a
ben> few hundred or more emails every day, things begin to slow
ben> down to molasses after a week or two each month,
[...]
ben> What can I do to help solve this? I know I can use an
ben> external archiver,
You could switch to weekly or daily archiving, I assume Pipermail supports that.
ben> but I don't know anything about that.
It's not that hard. I don't know much about this (jason, our Official Mail Guy, has taken an indefinite sanity leave so I'm learning more than I really wanna know), but what XEmacs does is to use the remnants of the former MLM like so:
In /etc/aliases:
main: "|/home/mailman/prog/wrapper post main",main-archive main-archive: "|/opt/majordomo/wrapper archive2-y2k.pl -a -M -f /opt/archive/majordomo/main
"/opt/archive/majordomo/main" is the directory holding the archives.
Of course you switch off Mailman's internal archiver. At least this gets the archiving hairball out of Mailman's pipeline.
The HTML stuff is done by wilma (Web Interface to List Mail Archives), a front end to mhonarc and glimpse. I don't know anything about that, but could check out the configuration if you want. Provides fairly nice searching, and is admittedly tuned to majordomo archives. Requires one cron job for reindexing.
"Stephen" == Stephen J Turnbull turnbull@sk.tsukuba.ac.jp writes: "ben" == Ben Gertzfield che@debian.org writes
ben> On a massive list (Mailman 2.0.6) I run that regularly gets a
ben> few hundred or more emails every day, things begin to slow
ben> down to molasses after a week or two each month,
ben> What can I do to help solve this? I know I can use an
ben> external archiver,
Stephen> You could switch to weekly or daily archiving, I assume
Stephen> Pipermail supports that.
Right, I guess there's just no archiver in the world that would support real-time archiving like this. In that case, I think it might be a better idea for pipermail to keep an eye on how long it's taking, and set a maximum for how long it spends on each message before it gives up and (possibly) tells the admin they need to switch to weekly/daily archiving.
I'll try and code up a patch to this effect; it's better than people claiming Mailman sucks and can't support large lists!
Ben
This problem occurs each time an admin attempts to set/remove the Digest option for a user. It's the version from CVS dated 7 sep 2001.
Bug in Mailman version 2.1a3
We're sorry, we hit a bug!
If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks!
Traceback:
Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 96, in run_main main() File "/usr/local/mailman/Mailman/Cgi/admin.py", line 158, in main change_options(mlist, category, cgidata, doc) File "/usr/local/mailman/Mailman/Cgi/admin.py", line 1316, in change_options mlist.setMemberOption(user, mm_cfg.Digests, value) File "/usr/local/mailman/Mailman/OldStyleMemberships.py", line 266, in setMemberOption self.__mlist.one_last_digest[memberkey] = cpuser File "/usr/local/mailman/Mailman/MailList.py", line 134, in __getattr__ raise AttributeError, name AttributeError: one_last_digest
Also, the admin is currently not receiving the requests to confirm subscriptions.
BTW. I'd like to upgrade to latest CVS, so, is there any way to get the Python "email" package separately? I'm unable to find it on Python site.
JA.
JA.
"JAA" == Jose A Accino jaccino@ieev.uma.es writes:
JAA> This problem occurs each time an admin attempts to set/remove
JAA> the Digest option for a user. It's the version from CVS dated
JAA> 7 sep 2001.
Very strange. I've had other reports of this, but I can't seem to reproduce this, either with a brand new list, or a list upgraded from 2.0.7.
JAA> Also, the admin is currently not receiving the requests to
JAA> confirm subscriptions.
I can't reproduce this either.
JAA> BTW. I'd like to upgrade to latest CVS, so, is there any way
JAA> to get the Python "email" package separately? I'm unable to
JAA> find it on Python site.
Actually, the latest email package is in the misc/ directory of cvs, but you can also get it at the mimelib SourceForge project.
-Barry
-
barry＠zope.com -
Ben Gertzfield -
Jose A. Accino -
Stephen J. Turnbull