On Wed, 1 Jun 2011, William Ashworth wrote:
A client of mine is looking to integrate more tightly to their Mailman
list. There's an archive page, but we're trying to format it nicely for
inclusion on their website so that it matches for members to see. I can
see two possibilities right now...
1. We write a custom PHP application to scrape and store the archive
pages into a database to call later, however we want.
2. We create an email address and subscribe it to the list. Any new
messages will be checked via a PHP script we build and stored in the
database, then we'll pull from our own archive format however we choose.
Assuming you have access to the Mailman installation, you can avoid both
of these somewhat cludgy steps and access the master archive directly.
Each mailing list keeps its archive as a big mbox-formatted file, which
you could presumably parse.
I also recall the ability to handle custom archiving (i.e. you can get the
system to archive messages in a way more useful to you). Mark will
probably have more to say about this possibility if it exists, assuming
there's nothing in the FAQ already about this.
You may wish to get the old messages out of the mbox master and then use
some kind of custom archive handler to handle new messages.
Mailman3 (still in development/alpha state) will probably make all this a
lot easier.
Geoff.
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
