On Fri, 10 May 2002, Jeremy Howard wrote: > Marc G. Fournier wrote: > > >Then again, someone mentioned in the other thread about having the perl > >check to see if a user wants the filter to do the checks or not ... but, > >in the content_filter itself, there is no concept *of* a user, so how > >would you do such a check? > > > > > In our content_filter we look at the RCPT TO: and check whether any user > in the list wants spam filtering. If they do, we run it through > SpamAssassin and add appropriate headers. Then in Sieve the actual > actions get taken. > > The only downside is that if you want per-user scores for each test, and > a message has multiple RCPT TOs, you have to decide which scores to use. > Generally you'd want to choose the lowest score for each test, to err on > the safe side. We consider this an acceptable downside, because it means > that we only have to run each SMTP transaction through SpamAssassin, > rather than each recipient through SpamAssassin. > > To avoid this, you'd have to deliver to an LMTP proxy and use > SpamAssassin there, rather than use an SMTP content_filter.
Ya, saw someone's thought about that ... that would definitely work instead of the spam extensions, but I don't believe the lmtp proxy supports that yet, does it?
