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.
That should not matter.. On the second-pass SA might decide they aren't spam and replace the X-Spam-Status header with one that says No, but it shouldn't ever corrupt a message as a result.
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 think you've more likely got some kind of problem resulting from lack of proper file locking.. Who/what/where does all this calling of winspam and replacing the message? are you absolutely SURE that NO other processes in the system can touch the message while this happens? What exact measures are taken to ensure this?
I suspect what is happening is you're calling winspamc from a MTA, or something of the sort. And the MTA begins re-delivery at the same time you're copying the message back over again... since the copying process deletes the original message before replacing it, there will be a short instance during which any process reading the message will get an empty message..
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
