I dug a little deeper and I found the following in the incoming log. For some reason,
any message flagged as spam by spamassassin
is some being recoginised by tmda as having Sndr: <> and therefore the message gets
through becuse of the incoming filter having the
line
from <> ok
the incoming log shows
Date: Fri Jun 6 17:22:01 EDT 2003
Sndr: <>
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subj: ***SPAM*** Liquid lust magic
Actn: OK (from <> ok)
looking at the headers of the message I don't see anything at all referencing a sender
of from of <>
everything looks normal.
does this have something to do with the fact that Spamassassin is a filter and is
outputing to stdout and therefore tmda is getting
confused and think that the message is coming from the local mailer-daemon <> or
something.
I'm at a loss, any suggestions or workarounds.
Bill
----- Original Message -----
From: "Bill Sandiford" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 06, 2003 6:38 PM
Subject: TMDA and Spamassassin
> I am trying to finish off my installation of Spamassassin and TMDA and I am almost
> there but I have one small problem.
>
> When Spamassassin flags a message as spam, that message is either:
> a) somehow getting through TMDA with out being confirmed, or
> b) TMDA is being bypassed altogether.
>
> I think the likely scenario is b)
>
> I am running Spamassassin globally with the following in my
> /usr/local/etc/procmailrc file:
>
> :0fw
> | spamc -f
>
> I am trying to run tmda on a per user basis from ~/.procmailrc which looks like this:
>
> SHELL=/bin/sh
> EXTENSION="$1"
> :0
> * EXTENSION ?? .
> {
> DELIMITER="+"
> }
> RECIPIENT="[EMAIL PROTECTED]"
> SENDER=`/usr/local/bin/formail -x Return-Path | sed 's/[<>]//g;s/^[ ]*//'`
>
> :0 w
> | /usr/local/bin/python /usr/local/tmda/bin/tmda-filter
>
> EXITCODE=$?
> DEFAULT=/dev/null
>
> What is the order or execution between /usr/local/etc/procmailrc and ~/.procmailrc?
> I assume that /usr/local/etc/procmailrc goes
> first. If so, does procmail still look at ~/.procmailrc if it exists
>
> The interesting part is that if Spamassassin doesn't tag the message as spam, then
> tmda functions properly (I can see
X-Spam-Status:
> No in the headers of the message in the pending directory) however if spamassasin
> tags the message as spam, then TMDA appears to
get
> bypassed.
>
> Any Ideas
> Bill
>
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
