[Exim] using $local_part in the acl for spam user

Top Page
Delete this message
Reply to this message
Author: Marques Johansson
Date:  
To: exim-users
Subject: [Exim] using $local_part in the acl for spam user
From: exiscan-acl-examples.txt.gz

  /* ---------------
  deny message = This message was classified as SPAM
          spam = joe
  ---------------- */


On the right-hand side of the spam condition, you can put the
username that SpamAssassin should scan for. That allows you to
use per-domain or per-user antispam profiles. The right-hand
side is expanded before being used, so you can put lookups or
conditions there. When the right-hand side evaluates to "0" or
"false", no scanning will be done and the condition will fail
immediately.

Why can't I use "spam = $local_part" ?


When I do I get: (in panic.log)

2004-01-13 09:23:33 1AgPS9-0005do-AT spam acl condition: cannot parse spamd output

( and in mail.log (spamd))

Jan 13 09:25:03 poe spamd[26920]: connection from localhost [127.0.0.1] at port 60355
Jan 13 09:25:03 poe spamd[21770]: bad protocol: header error: (User header contains control chars)



--
Marques Johansson
marques@???


Q:    What is green and lives in the ocean?
A:    Moby Pickle.