Okay folks, 1.0b11 is now available at www.list.org. This is
basically a bug fix release addressing problems with case-preserving
addresses and archiving of Usenet gated newsgroups. For you hardcore
debugging types, there's a new script called bin/withlist which you
can run like so:
% cd ~mailman
% python -i bin/withlist mylist
Loading list: mylist (unlocked)
withlist leaves you with a global variable `m' which is the MailList
object you opened. Give withlist and optional second argument if you
want the list to be locked.
A note about upgrading. I had to bump the DATA_FILE_VERSION number so
that the config.db got updated to deal with case-preserving addresses
in some situation. I've been running this on python.org for a few
days now and it all seems to work, but please keep an eye out for
anything strange with your config.db file.
I'm running mailman 1.0b10
This is all I get from a who request.
---------- Forwarded message ----------
Date: Wed, 31 Mar 1999 10:48:22 +0200
Subject: Mailman results for linux-flame
> Barry A. Warsaw bwarsaw(a)cnri.reston.va.us writes:
> Is anybody currently gating Usenet to a mailing list, /and/ doing
> archiving with the default Pipermail?
I am not yet using Mailman to do this, but I am doing the same thing with a
hairy custom setup (majordomo + MHonArc + INN + gateway scripts). In about a
month or so, I plan to switch our setup over to Mailman since it is *so* much
> I would rather not add this hack to Mailman unless a lot of people
> would benefit from it.
We have a number of people who choose to interact via our local Usenet groups,
and it is important that their contributions are archived. Without the ability
to do so, I will need to stay with our current setup (icky as it is from an
administrative standpoint, it does what I need) instead of moving to Mailman.
Let me just say that Mailman is a wonderful piece of software. I have poked at
it a little bit on a test installation, and it is beautifully conceived and
1975 Cahaba Valley Road (205) 988-4268
Indian Springs, AL 35124 benjy(a)alum.mit.edu
Is anybody currently gating Usenet to a mailing list, /and/ doing
archiving with the default Pipermail? If so, you may not have noticed
that the archives are pretty broken; nothing that originates on Usenet
will show up in the archive.
I believe I understand why this is happening, and although I don't
have a fix yet, it shouldn't be too difficult. I should be able to
get it into 1.0b11. The problem occurs because Pipermail uses
Python's mailbox.UnixMailbox objects which expect "From " separators.
Message that originate on Usenet don't have these envelopes. The
patch should be to simply synthesize these on messages gated off the
However, there's a more severe breakage. You've actually lost
information that is hard to reproduce because the flat listname.mbox
files don't have the separators in them either. Running bin/arch over
the file will give you even more corrupt archives (the incremental
archiver just throws the Usenet messages away; bin/arch will tack them
onto the last email-originated message).
What you could do is to trek through the listname.mbox file looking
for Newsgroup: headers (which appear, but I don't think are
guaranteed, to be the first header in the message). When you find
one, you jam in a synthesized "From " envelope.
I would rather not add this hack to Mailman unless a lot of people
would benefit from it. For the test lists that I'm running, we're
willing to just trash the archives and start over; the lists aren't
live anyway. I'd like to know who would be really adversely affected
by this problem.
On Wed, Mar 31, 1999 at 02:23:14PM -0500, Barry A. Warsaw wrote:
> Modified Files:
> Log Message:
> DeliverToList(): Strip off any duplicate Sender: headers, leaving just
> the one pointing to the list-admin.
The same problems occurs with Errors-To, haven't checked agains
Edgard Castro <castro(a)usmatrix.net> | 305-273-5003 -o)
Chief Network Engineer - U.S. Matrix Internet, Inc. /\\
Linux Counter User #29078 -- http://counter.li.org _\_V