failure archiving large majordomo mbox

[Potstickr]

I have a 360MB listname.mbox file, which is
concatenated from six years of
majordomo archives. I tried archiving the mbox using
bin/arch (via the
built-in pipermail), and got this:

Traceback (most recent call last):
  File "bin/arch", line 129, in ?
    main()
  File "bin/arch", line 118, in main
    archiver.processUnixMailbox(fp, Article)
  File "/home/mailman/Mailman/Archiver/pipermail.py",
line 526, in processUnixMa
ilbox
    a = articleClass(m, self.sequence)
  File "/home/mailman/Mailman/Archiver/HyperArch.py",
line 207, in __init__
    self.__super_init(message, sequence, keepHeaders)
  File "/home/mailman/Mailman/Archiver/pipermail.py",
line 175, in __init__
    self._set_date(message)
  File "/home/mailman/Mailman/Archiver/HyperArch.py",
line 419, in _set_date
    self.__super_set_date(message)
  File "/home/mailman/Mailman/Archiver/pipermail.py",
line 228, in _set_date
    date = message.getdate_tz('Date')
  File "/usr/pkg/lib/python2.0/rfc822.py", line 371, in
getdate_tz
    return parsedate_tz(data)
  File "/usr/pkg/lib/python2.0/rfc822.py", line 828, in
parsedate_tz
    if data[0][-1] in (',', '.') or
string.lower(data[0]) in _daynames:
IndexError: list index out of range

I'm running Mailman 2.0.8 on Python 2.0, NetBSD 1.5.1.
I've applied these
patches:

  mailman-2.0.8-plaintext-0.16.patch
  indexing-2.0.6.patch
  htdig-2.0.8-0.1.patch

The mbox has some older messages for which pipermail
apparently punts,
setting their date to February 2002. I will look into a
work-around which
splits and then rebuilds the mbox with better date
formatting. Not sure how
to go about that...

[http://sourceforge.net/tracker/index.php?func=detail&aid=518083&group_id=103&atid=100103]

[Barry Warsaw (barry)]

Try Mailman 2.1. A lot of fixes have been added to
Pipermail, and while it's still not perfect, it should be a
lot better.

[Potstickr (potstickr)]

I'm a little spooked about trying it just to get pipermail
working. How close is 2.1 to release quality?

Morgan