Defrosting Spam

I have a message that I want to come through, because it is not Spam. It gets deleted and "frosted." I open XQMWin to defrost it... well, about 30 seconds later, its right back in XQMWin. Its been marked as spam a second time. How do I get it to bypass the Spam filter when I am defrosting it. The only way I know how is to delete SAFilter from filters.in.tab, defrost it, then add it back into SAFilter. I mean, it seems kind of ridicoulous to have to do this. I thought defrosting meant that you checked out the message, everything was fine and dandy, so let it go. Is there another way?

Jason

Whys it say it's frozen ?

I have the same issue with some of the messages and not all of them.

I guess you'll have to change the script to first check if the message has already been scanned for spam or not (by looking into the headers). Some scripts do this check already for completely other reasons, but I guess it would also solve your problem.

But if you're not much of a coder, I guess all you can do is hope someone else updates SAFilter, or look around for an other filter.

The only time I haven't been able to unfreeze a message is when the Xmail header lines from the spool file where missing. You's might want to check out why the files been froze.

Ps. SA should rescan a message it already has. It looks for the X-Spam headers and if Autolearn it turned on it records a check sum of every message that passed though it so as not to re count it. And throw off it's learning.

I'm not sure why SA should rescan an already scanned message. I have added a check to prevent this in my script, to reduce CPU-load.
Obviously you should look for some server specific peace of header that gets added, otherwise spammers could make their spam look as if it has already been scanned.

If you can convice me that there is a good reason to re-scan a message, I'd like to rethink this.

But it seems to me that, if you want SA to rescan a message when you defrest it, it will inevatably freeze the message again if it was frozen because it turned out to be spam the first time.

I'm sorry i meant it shouldn't rescan a message. Sorry about that.

Hmmm... I guess I have to put the part back into the script that put that header flag in there. I removed it, because I didn't want stuff crowding up the headers, for example, just to say it wasn't spam... I will try that.