SAProxy has successfully caught all fifteen pieces of spam that have arrived since I installed it on Friday, with no false positives. That’s good. What’s bad is that it has a habit of dying while I’m away from the computer.<\/p>\n
My computer runs XP Pro unattached to a Windows domain, so that we can use the fast user-switching features. (Sometimes it’s faster for Abi to just log on to my computer and check her email rather than switching on her laptop.) What I’ve been finding is that when I come back to my session after being away for a couple of hours, whether another user session has taken place in that time or not, SAProxy will be gone, and I have to restart it.<\/p>\n
I don’t know if it’s crashing or if it just figures that I don’t need it any more. It doesn’t leave behind any log files, nor does it write to the Windows Event log, so I just have no idea.<\/p>\n
For the volume of spam I receive (low, by all accounts), I think it’s probably less annoying to just delete it when it arrives rather than to restart SAProxy whenever I resume a session. It should be running as a service rather than as a user program anyway. I reckon I’ll give it another chance when the product has matured a bit.<\/p>\n