On Thu, Sep 23, 2004 at 01:51:54PM +0100, Anthony Edwards wrote:
> I have also been unable to persuade spamd to add spamassassin headers,
> as per my posting of last night to the list. Running spamassassin, in
> contrast, seems to work properly (which seems to rule out it being a
> local configuration issue?).
I have just stopped spamd, removed ~/.spamassasin completely, and
removed all instances of local* in /etc/mail/spamassassin so that no
old configuration files from the previous version (2.64) could be
affecting things.
Next, I restarted spamd, and fetched some mail with spamc being called
by .mailfilter (maildrop configuration file) as normal. An example
of the result (from /var/log/mail.info):
Sep 23 13:58:29 ultra spamd[8586]: processing message
<[EMAIL PROTECTED]> for anthony:500.
Sep 23 13:58:30 ultra spamd[8574]: identified spam (12.4/5.0) for
anthony:500 in 3.9 seconds, 15975 bytes.
Sep 23 13:58:30 ultra postfix/local[8331]: 7BB7033DD6:
to=<[EMAIL PROTECTED]>,
orig_to=<[EMAIL PROTECTED]>, relay=local, delay=44, status=sent
("|/usr/local/bin/maildrop")
spamd apparently identified the mail as spam, with a score of 12.4.
However, no spamassasin headers were added, and as a result my
.mailfilter line:
if (/^X-Spam-Flag: YES/)
to Mail/junk
Had no effect (of course), and the mail was delivered by maildrop to the
default mailbox.
--
Anthony Edwards
[EMAIL PROTECTED]
