For those of you on majordomo-workers who aren't on majordomo-users, I
proposed to add a mechanism to filter postings to the program resend. I sent
that proposal to the wrong list, for which I apologize. Followups to this
should go to the -workers list.
Once I add something to Majordomo it's stuck there forever (eg. get and
index). I'd rather get a little more experience with filters before I
propose something permanent.
After reading the replies, I've decided the concept is good, the
implementation I described was lousy. A better trial implementation would be
in a separate program. I'll call it "postingfilter", although it needs a
This would keep the code entirely separate from Majordomo, and thus not
slow down majordomo-2.0 development. Likewise, the postingfilter could
be put into use much sooner.
Adding new filters is something that can only be done by trusted local
users. I believe that this provides a large enough testing base to be
usefull, I realize it is not good for the long run.
System administrators can change the aliases file, so that postingfilter is
invoked instead of resend. Each filter would just be a plug-in module you'd
stick in some directory unique to each list. Postingfilter would pipe the
message through each filter. The last filter in the chain would invoke
To keep the majordomo-workers mailing list pure, I have created a new mailing
list, firstname.lastname@example.org, for discussing the details of postingfilter.
If you're interested, subscribe by sending "subscribe postingfilter" to
Paul Haas email@example.com Web site: http://www.hamjudo.com
Home: (313) 487-8739 Office: (313) 487-4357 Fax: (313) 487-4371
Finger or email my hottub at firstname.lastname@example.org, seen on TV