--- Begin Message ---
Thanks for the help. I am useing CommuniGate ,clamav, and
scanspam.sh to call spamc/spamd, in the rules I am
checking for the SA header to prevent looping the message
in the queue. Never thought that this would happen. If I
read the docs right I can create a custom header message
that I can have SA add to my messages to prevent message
looping, right?
Jonn
On Tue, 27 Dec 2005 15:10:39 -0500
Matt Kettler <[EMAIL PROTECTED]> wrote:
Pollywog wrote:
On 12/27/2005 02:56 pm, Matt Kettler wrote:
At 08:48 AM 12/27/2005, Jonn R Taylor wrote:
How can I make this go thourgh SA when it thinks it
allready has????
Why wouldn't it go through SA?
SA doesn't have any built-in behaviors that will prevent
it from
re-scanning a message.
I had a similar problem with clamassassin headers, so I
had Postfix remove
them so that my Maildrop filters would not be confused.
I just set the
clamassassin headers to IGNORE in Postfix's
header_checks, IIRC.
Could something like this be done for Spamassassin's
headers, by the MTA and
would it solve the problem?
Why bother? SA isn't confused by them. No sane
spamassassin setup would ever
have this problem. Period.
The problem lies in a user intentionally trying to
bypass SA for already scanned
mail. The fix lies in not doing something so foolish in
the first place.
Fix the problem in the implementation, don't cover it up
by modifying the input
data to hide the existence of this problem.
--- End Message ---
