Since most of our lists are used as moderated distribution lists and are
synchronized via scripts, it wasn't very difficult.
You have your standard mailman list aliases - which we partition into their
own alias file /etc/mail/aliases.mailman
fubar: "|/opt/mailman/mail/wrapper post fubar"
fubar-admin: "|/opt/mailman/mail/wrapper mailowner fubar"
fubar-request: "|/opt/mailman/mail/wrapper mailcmd fubar"
fubar-owner: fubar-admin
We have another set of aliases - these are partioned into
/etc/mail/aliases.hypermail
fubar-archive: "|/opt/bin/hypermail -i -u -d
/opt/mailman/archives/private/fubar \
-c /opt/mailman/archives/private/fubar/fubar.rc
I've written scripts to create a base hypermail archive from a template
using sed (which creates "fubar.rc") at the same time a new list is created.
This is probably the most complicated part of hypermail since the config
file overrides the command line parameters. Adding this alias is only
necessary if you want the archives in synch at all times. You could just
regenerate the archives nightly.
The built-in mailman command "arch" can be used to recreate a pipermail
archive from its mbox - I wrote a similar script for hypermail.
I use the site settings of
ARCHIVE_TO_MBOX = 1
PUBLIC_EXTERNAL_ARCHIVER = 0
PRIVATE_EXTERNAL_ARCHIVER = 0
which maintains the internal pipermail "backup" to mbox format.
If necessary, you can edit the mbox format with Pine using "pine -f
/opt/mailman/fubar.mbox/fubar.mbox" and then regenerate the archives.
Scott
> is this a basic feature or have I missed a tip and how does it work?
> thanks
> chas
>
------------------------------------------------------
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
