RE: [SAtalk] When not to call SA

2003-12-23 Thread Robert Lacroix
llel processing. The files are totally empty when returned from winspamc, so size = 0. The return path stuff is added by your mailserver afterwards. /robert From: Frank M. Cook [mailto:[EMAIL PROTECTED] Sent: Dienstag, 23. Dezember 2003 19:14 To: Robert Lacroix Cc: SpamAssassin Subject: Re: [SAta

Re: [SAtalk] When not to call SA

2003-12-23 Thread Frank M. Cook
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 mail

Re: [SAtalk] When not to call SA

2003-12-23 Thread Frank M. Cook
> What version of SpamAssassin? 2.61 > Could the problem possibly be more than one messages trying to be scanned > at the same time? yes, I think that could happen. my mail software is calling an external batch file which creates a separate instance of each scanning batch file for each message t

RE: [SAtalk] When not to call SA

2003-12-23 Thread 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

Re: [SAtalk] When not to call SA

2003-12-23 Thread Evan Platt
--On Tuesday, December 23, 2003 10:52 AM -0500 "Frank M. Cook" <[EMAIL PROTECTED]> wrote: > > 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 proble

Re: [SAtalk] When not to call SA

2003-12-23 Thread Matt Kettler
At 10:52 AM 12/23/2003, Frank M. Cook wrote: 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 alr