Any reason DELIVERY can't be set in the .tmda/config? This file is pure Python code, so you can get as fancy and dynamic as you want.
Ah, I didn't realize you could put code in there.
Which mailing list the message is intended for can often be gleaned by looking at the environment (i.e, $LOCAL and/or $EXTENSION on Postfix).
Our aliases are configured so:
foo: "|tmda-filter -D [EMAIL PROTECTED]"
foo-listserv: "|/etc/foo/wrapper resend -l foo -h
xiph.org foo-outgoing"
foo-outgoing: :include:/etc/listserv/lists/foo,
"| /etc/listserv/wrapper archive2.pl -a -m
-f /var/spool/mail/archive/foo",
"|/etc/listserv/wrapper hypermail -i -u
-c /etc/listserv/lists/foo.archive"so it's nice to be able to set these things explicitly and treat tmda as a black box.
How does the mailman integration work on the tmda lists? Having subscribers automatically whitelisted seems like a nice feature.
-r
_________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
