On Wednesday 15 March 2006 13:59, Barry Warsaw wrote:
> On Tue, 2006-03-14 at 12:44 -0800, Andrew D. Clark wrote:
> > I've made a small patch to HTMLFormatter.py to provide for a canonical
> > (aka lowercase) list name. This is handy for a variety of reas
On Tuesday 14 March 2006 14:53, Rich Johnson wrote:
> On Mar 14, 2006, at 3:44 PM, Andrew D. Clark wrote:
> > I've made a small patch to HTMLFormatter.py to provide for a
> > canonical (aka
> > lowercase) list name. This is handy for a variety o
I've made a small patch to HTMLFormatter.py to provide for a canonical (aka
lowercase) list name. This is handy for a variety of reasons.
383a384
> '' : self.real_name.lower(),
I don't really care if it is called mm-lc-list-name or mm-canonical-list-name
or what not, I simply find
--On Friday, July 01, 2005 02:25:28 PM -0400 Barry Warsaw
<[EMAIL PROTECTED]> wrote:
> On Fri, 2005-07-01 at 13:30, Andrew D. Clark wrote:
>
>> I consistently get shunted messages with errors like so in
>> logs/errors:
>
> Andrew, what version of Mailman? If no
Hi,
I consistently get shunted messages with errors like so in logs/errors:
Jul 01 10:28:39 2005 (26124) Uncaught runner exception: 'ascii' codec
can't decode byte 0xc5 in position 0: ordinal not in range(128)
Jul 01 10:28:39 2005 (26124) Traceback (most recent call last):
File "/home/service
like this cause termination or should they usually be
caught by the caller etc.. ?
Cheers,
-Matt Helsley
On Wed, 24 Sep 2003, Andrew D. Clark wrote:
I can't remove a member address like this:
%./remove_members -n -N some-list "[EMAIL PROTECTED] * ben"
Traceback (most rec
Hello all,
I've encountered some list member addresses like so (I've substituted
the domain name here to protect the guilty):
%./list_members some-list
[EMAIL PROTECTED] * ben
I can't remove a member address like this:
%./remove_members -n -N some-list "[EMAIL PROTECTED] * ben"
Traceback (most
Seems like the problem may not actually be with bin/arch, but rather
the standard archiving. The list in question currently has a backlog
in the archive queue (around 950 files), and the index.html file being
generated by the archiving only lists last month (probably because the
messages it's
bin/arch still seems to have trouble with large mbox files (448 MB in
this case). It actually does finish processing the archive, which is
an improvement over 2.1 betas, but the index.html file that it
generated only has a link for one month worth of archives.
Another interesting problem is tha
Under Mailman 2.1b5, when I run bin/arch on one of my lists for which I
turned off pipermail archiving during the
2.1b3-pipermail-archiving-performance-sucks-badly period it dies
complaining:
"unknown encoding: big5_tw".
The mbox for this list is huge, and I'm having trouble locating exactly
w
I love answering my own questions. Either that, or I'm far too hasty
posting problems to the list before I try to fix them. In anycase,
hopefully this will help anyone else who is having problems regenerating
their archives.
Try renaming the html archive directory for a given list to listname.
A few more lists, a few different errors:
Traceback (most recent call last):
File "./arch", line 173, in ?
main()
File "./arch", line 163, in main
archiver.close()
File "/home/services/mailman/Mailman/Archiver/pipermail.py", line 303, in
close
self.update_dirty_archives()
File "/home/
I've had bin/arch croak on a few different list archives (though for one of
the lists, it worked the 2nd time I ran it, so that's good!) with the
following error:
Updating HTML for article 2
Traceback (most recent call last):
File "./arch", line 173, in ?
main()
File "./arch", line 163, in
--On Wednesday, November 13, 2002 18:40:22 -0500 "Barry A. Warsaw"
<[EMAIL PROTECTED]> wrote:
"DM" == Dan Mick <[EMAIL PROTECTED]> writes:
>> BTW, I usually run current cvs on my personal domains, and very
>> nearly cvs on python.org, so if there's a serious regression in
>> cvs,
I'm wondering how soon I might expect Mailman2.1b5 (or 2.1 final!) to be
cut loose. I'm running 2.1b3 and, AFAIK, the bugs I'm looking to have
fixed (poor archrunner performance, esp) aren't fixed in 2.1b4, but I'm a
bit leery of a CVS build on a production mailing list system. Can Barry,
or
I've had the same problem. ArchRunner seems to have serious performance
problems if you've got heavy list activity and are archiving to both
pipermail and mbox. I "fixed" it by setting ARCHIVE_TO_MBOX=1. This will
only archive to mbox, so your pipermail archives won't be updated. You
should
16 matches
Mail list logo
