Tuesday 23 May 2006 04:22 skrev Zafer Aydogan:
> acl_check_data:
>
> warn spam = nobody
> message = X-Spam-Score: $spam_score\n\
> X-Spam-Flag: $spam_report\n
>
> #X-Spam_score_int: $spam_score_int\n\
> #X-Spam_bar: $spam_bar\n
> #X-Spam_report: $spam_report
>
> # Accept the message.
>
> accept
>
> ------
>
> spamcheck_router:
> no_verify
> check_local_user
> condition = "${if and { {!def:h_X-Spam-Flag:} {!eq
> {$received_protocol}{spam-scanned}}} {1}{0}}"
> driver = accept
> transport = spamcheck
> -----
>
> spamcheck:
> driver = pipe
> # batch_max = 100
> command = /usr/sbin/exim -oMr spam-scanned -bS
> use_bsmtp = true
> transport_filter = /usr/bin/spamc
> [...]
> user = mail
Your configuration looks a bit weird. Is it intentional that you call SA both
in the ACL and in the spamcheck transport? One of the benefits of the content
scanning extension is that you don't need this kind of mess. A drawback is
that it's impossible to apply user preferences except by accepting only one
recipient per incoming message. On the other hand, content scanning in ACLs
is the only way to go if you want to reject spam at SMTP time, which is a
good idea. And your spamcheck transport doesn't let SA aply user preferences
anyway.
--
Magnus Holmgren holmgren@???
(No Cc of list mail needed, thanks)
