Bob Tanner <tanner at real-time.com> writes: > Here is my plea to the list again. :-) > > As I sit around waiting for Sprint to call back, I started to go through my list > of low priority tasks. After buying a Ferrari, was mailman archives. > > My last post was about how mailman stores all posts in mbox format(!), yet 1 big > o'file. And pipermail plows through the file to generate the date, thread, raw > and compress raw archives. Not the best design in the world. > > My first problem is several of the mailing lists have mbox-es approaching the > magical 2Gb size. The work around of that will be to go reiserfs or ext3 for the > large file support. > > The second problem was backing the mbox files up. On a very active list, the > mbox is changing so it's hard to get a clean backup. Don't know if reiserfs or > ext3 have snapshot capabilities or if I have to do lvm or, or, or. But I got > around this by not allow pipermail to run from 2am - 7am so the backup can dump > everything. > > So any mailing list packages that are like mailman, but using a relational > database on the backside for archives? > > I think that would be idea. Well, I'm not sure that "like Mailman" is accurate. But ezmlm+idx (which requires qmail to work, which may be another problem for you) handles archives very well IMHO. I'm using the filesystem version, where the archives are divided among directories (100 files per directory). There is an SQL version as well, but I have not used it; I don't know if that moves the archives to the database, or only the mailing list subscription (and pending) information. -- David Dyer-Bennet, dd-b at dd-b.net / Ghugle: the Fannish Ghod of Queries Book log: http://www.dd-b.net/dd-b/Ouroboros/booknotes/ Photos: http://dd-b.lighthunters.net/