On Thu, 9 May 2002, Marc G. Fournier wrote: > So, unless I'm overlooking something, is there some way of injecting 'per > user' options at the lmtp (and beyond) level?
Sieve scripting allows such flexability: Want to disable the filter? Don't filter on the header that SA injects. Want to whitelist a mailing list? Don't apply the SA header filter to messages from that address. What to set a different threshhold? Use the comparison extention (which was discussed earlier, it's not implemented but it's probably something we want). The key is that SA can put enough information in the header to let sieve have pretty fine-grained control over the message. -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 235 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper
