From: Mark M. <Mar...@ij...> - 2003-04-25 18:50:44
|
Ricardo, | We don't care about viruses - that is, all get blocked, period. But for | SPAM, some like it, so basically, I'll need to define the following: | | Spam checks, in this order: | 1) Check LDAP with per user setting (bypass, tag/kill levels, etc. | 2) Check some manually added (amavisd.conf) users (bypass, tag, etc.) | 2) If not found, use a default (tag only). | | I understand how to set these up on the LDAP side of things, but not | sure on the order, The order is hard-wired: SQL, LDAP, hash, ACL, RegExp, and maybe some default. | and where to check the manually added ones after | (recepient addresses). Not sure I understand the question. | Of course, what happens if LDAP is down (for whatever reason) in this | case ? I assume, it'll skip to the next check in order, right ? No, I believe it will all grind down to a stand-still. | Also, looking a bit at the code, it seems we are missing a SPAM TAG 2 | level, but just SPAM TAG and SPAM KILL levels... But there is one: $spam_tag2_level_sql and $spam_tag2_level_ldap. Maye sure you look at the -p1 patch release code, as there were a ldap patch that went in. Mark |