>>>>> "BH" == Bill Houle <firstname.lastname@example.org> writes:
BH> If I read you right, you are suggesting a sort of script wrapper around
BH> mj_shell to do these 'fringe' functions from the local server, whereas
BH> I was suggesting that Mj2 have the hooks to support the fringe
BH> functions from within (accessible for list admins w/o local system
Well, I'm suggesting that you can accomplish what you want by writing
scripts that call mj_shell to do things. You can do lots of things, even
send list mail, through the shell interface.
BH> This could make Mj2 into a killer "targetted email" server, which has
BH> negative Spam-ish connotations but in fact has incredible potential for
BH> success in large corporations.
Well, I know little about success in large corporations, but how about a
Allow a way to push a 'filter' to the backend database. We already have
zubscription classes and we generate the list of addresses to mail to on
the fly so this isn't really difficult. A simple example of a filter might
be a regexp to select addresses to send to.
How would the filter be specified? This isn't difficult for the shell
interface; just make it an option to the post command. But for the email
interface, the logical choice is a header except that too many crappy MUAs
don't let you specify headers. Another choice would be to use the mailbox
Unfortunately this interferes with qmail support. I won't lose sleep over
qmail's poor choice of mailbox separator, though.
What format does the filter take? I have no idea. I'm happy to not
specify it and let it be specific to the backend.