![](https://secure.gravatar.com/avatar/334b870d5b26878a79b2dc4cfcc500bc.jpg?s=120&d=mm&r=g)
"BAW" == Barry Warsaw <barry@python.org> writes:
* You could still add a handler to the global pipeline, but have
it do a test of the listname or domain first, and if it doesn't
match, do a quick return. You pay the cost of the handler for
every mailing list, but it should be fairly minimal in the
scheme of things
I once added a maybe-log-and-return handler at every point in the pipeline on our busiest list. No effect on load. I dunno, if you're handling a million posts a day you might notice that. But handler calling is way down in the scheme of CPU suckers compared to spam and virus filtering.
I'm unwilling to add to the global pipeline simply because there's no such thing as a 100% safe edit, not because I'm worried about function call overhead in Python.
-- School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.