RE: [SAtalk] When not to call SA

[Robert Lacroix]

Hi,   I am having the same problem with winspamc. I changed my script to check every return of winspamc against something like "if size = 0 then send "input_message" instead of "temp_file"". That sends the message unchecked instead of completely empty. But I doubt it has something do to with mails that were already checked, I think it's a random error of winspamc :)   /robert   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frank M. Cook Sent: Dienstag, 23. Dezember 2003 16:53 To: [EMAIL PROTECTED] Subject: [SAtalk] When not to call SA I'm having a problem with blank messages.  Sometimes the source only shows a return path.  I think it may be a spamassassin issue.  I'm using winspamc and the guys on their forum suggested the problem might be caused by checking messages that have already been checked such as forwarded messages.   Technically what I'm doing is a winspamc < input_message > temp_file and then overwriting the input message with the temp_file if the error code says it was spam.  Assuming the problem is indeed messages that have been checked before, should I just delete anything that is tagged X-Spam: Yes before calling spamassassin?    I don't suppose it's safe to skip testing anything tagged X-Spam: No as the spammers could just put that in their messages.  Is there something some header line to look for to skip SA testing?   Frank M. Cook Association Computer Services, Inc. http://www.acsplus.com