[Mailman-Users] Re: Mailman-Users digest, Vol 1 #760 - 11 msgs
Christopher P. Lindsey
lindsey at mallorn.com
Tue Sep 19 09:29:01 CEST 2000
> This is a great example of why mailman ought to either send messages
> to the moderator for approval, or auto-reject them, if they are
> replies to the digest with the digest subject unchanged.
You could always wrap your lists with procmail or some other type of
filter (personally, I prefer this option -- I feel that it's the UNIX
way to use other tools to bolster the performance of programs... That's
what pipes are for, right? ;) (of course, the emacs people would
probably disagree :)
http://www.python.org/pipermail/mailman-users/1999-February/000617.html
Although this doesn't make use of the Web interface, you could use
the 'mailowner' command with wrapper to just send the email to
listname-admin. Once you get it, you could change the subject and
pipe it off to sendmail with -f set to the original sender's envelope
from header.
# set to your mailman install dir
PREFIX = /home/staff/mailman
:0
* ^Subject: Mailman-users digest, Vol [0-9]+ #[0-9]+ - [0-9]+ msgs
| $PREFIX/mail/wrapper mailowner Mailman-users
Or more generally (note, this is untested):
# pull the name of the list into $MATCH, then call as arg to wrapper
:0
* ^Subject:[ ]+\/[^ ]+ digest, Vol [0-9]+ #[0-9]+ - [0-9]+ msgs
{
SUBJECT = $MATCH
:0
* SUBJECT ?? ^()\/[^ ]+
| $PREFIX/mail/wrapper mailowner $MATCH
}
Ultimately, I'd like to see wrapper take an argument 'webadmin' that
sticks the message into the Web-based admindb holding area. Adding
that functionality to wrapper is easy enough, but I haven't looked
at the Python internals for this yet...
Chris
More information about the Mailman-Users
mailing list