On Fri, Oct 23, 1998 at 03:15:36PM -0500, Christopher Lindsey wrote:
Return-Path: <owner-mhonarc(_at_)ncsa(_dot_)uiuc(_dot_)edu>
From: Christopher Lindsey <lindsey(_at_)ncsa(_dot_)uiuc(_dot_)edu>
To: alago(_at_)galeno(_dot_)unicies(_dot_)cesga(_dot_)es (Alvaro Jose
Fernandez Lago)
Cc: mhonarc(_at_)ncsa(_dot_)uiuc(_dot_)edu
...
PD: I use X-Mailing-List header in the recipe, but that´s
something I would like people comment on. Maybe Resent-From ?
I'm going to turn this into another procmail mailing list... :)
I've found that X-Mailing-List: doesn't always exist; sometimes
it's From_, Sender:, or Delivered-To: that I end up having to
use. And of course, they all have different formats... In a
I have found that Return-Path: works for almost every mailing list
that I have been subscribed to. The one exception I have seen was
a list that was run manually by someone. A simple procmail recipe
such as
:0:
* ^Return-Path:.*owner-mhonarc
mhonarc
almost always works for me. If you want to automatically archive list
messages, you can use a wrapper script:
:0:
* ^Return-Path:.*owner-mhonarc
| /usr/local/bin/mha-rdmsg mhonarc
Where mha-rdmsg is a wrapper script, loosely based on the run_mhonarc.pl
script that Earl Hood posted here a week ago. All the list specific
configuration knowledge and resource variable setting for each list
to be archived is in the mha-rdmsg script. If you are doing this
on the system which is hosting the mailing list, you can have the
list server pipe the message to the wrapper program, and add to
the MHonArc archive at the same time you add it to the list server's
archive. I am working on setting up MHonArc archives for some
lists I maintain; however I don't currently do on-the-fly archive
updates, since there are some issues regarding the uid/gid that
sendmail runs as, versus the ownership of the MHonArc archives,
which I haven't yet resolved. I am leaning towards doing a nightly
-add run over the current majordomo archives for each list.
Wayne Chapeskie
