Johann Spies wrote: > On Mon, Mar 10, 2008 at 10:32:43AM -0400, Marc Sherman wrote: >> You should probably rework your config so that it only checks the spam >> condition in the first stanza; the $spam_* vars will carry over to >> future stanzas, so that you can add multiple headers. Your current >> config will fail in the case of a spamassassin error; it will attempt to >> rerun the spam check for each spam=spamd:true check, so if there's a >> recurring spamassassin failure, it will churn a lot of resources. > > I was wondering about that. The examples in the exim documentation > also calls spamassassin several times:
If you keep the "spam = user" verb/condition/thingy the same each time it is called (just keeping the user the same, you can add/remove the true bit), the result is cached and only calls SA once so it's no less efficient than any of other condition. I use it for a yes/no condition in my spam ACLs. There's probably about 101 ways to do the same check. -- The Exim Manual http://www.exim.org/docs.html http://www.exim.org/exim-html-current/doc/html/spec_html/index.html -- ## List details at http://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
