Jan. 29, 2006
2:13 p.m.
"Mark" == Mark Sapiro <msapiro@value.net> writes:
Mark> The problem I see is that while header_filter_rules are in
Mark> the Spam filters section of the admin interface and enforced
Mark> by a module named SpamDetect, they can actually be used in
Mark> other ways to reject messages which are not 'spam' per se.
I'm tempted to say that in that case the logic should be moved to a separate module, which is imported to SpamDetect with the restriction that REJECT is not available, while another Handler is created for PolicyFilters. They maintain separate rule lists etc.
Sound like a lot of work when simply documenting that spam should _never_ be rejected should be enough.<wink>
-- 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.