Thanks for reporting Tribble! It probably is working but it sounds like on the second run Bayes picked up on something in the headers which made it think the spam was ham. That could be because you forwarded or bounced the mail to yourself. For example, if you look in the headers of the original email you're unlikely to find anything like:
X-Mailer: Poco3 Beta (1965) - Licensed Version
But if you look in the headers of the email you forwarded/bounced to yourself you will find something like that. If you then look in DBGood.ini you'll see it (probably) has an entry:
X-MAILER-poco3
So that a header like that will affect the Bayes score and will probably make the mail look less spammy (unless you have lots of people spamming you from PocoMail!).
You may like to change the option "Use new style headers?" in the Setup Script screen for this script to False. The Bayes filter could be tipped by the headers this script generates and setting that option to False should minimise that chance. On the other hand, some people (Vamp!) want Bayes to be affected by the headers this script generates so for him he'll want it set to True. If you find yourself receiving lots of email like this then you could alter the scores this script gives so that even without Bayes it will be classified as spam, but then that increases the chance of it making mistakes too.
So to summarise, your message was probably border line spam according to Bayes and something tipped the classification towards the ham direction when you received it the second time. What exactly that was i don't know but theres a couple of ideas for you.
What definitely would help is if the Bayes filter could be forced to train on messages that this script classifies as spam. If anyone knows how to do that please say
