The day before yesterday, James Farmer released a new beta release of SpamPal. The version number has reached 1.73g and the program can be downloaded as installer or into zip format. SpamPal is an anti-spam program for Windows that sits between the e-mail client and the mailbox, so to speak, and is intended to identify spam and mark it as such. This marking can then be used in your favorite e-mail program to create a filter that, for example, puts this e-mail in a separate folder or immediately discards it. Fixed several issues in this release, including one in the transparent proxy that frequently caused Mozilla Thunderbird to crash. The full changelog looks like this:
Changes in 1.73g (Beta Release)
- Service configuration files:
- New registry key: HKEY_LOCAL_MACHINE\Software\SpamPal for Windows\SpamPal\ServiceConfigDirPath can be used to set location of Service configuration data without affecting instances of SpamPal that execute as an application.
- By default, new service installations now store configuration in “All Users\Application Data\SpamPal” rather than “LocalService\Application Data\SpamPal” – for existing users, the ServiceConfigDirPath registry key should get set automatically so your service still finds your old configuration . This should prevent the service configuration moving between LocalService and NetworkService folders occasionally. (Thanks to George Breese for his great diagnosis of this problem!)
- SMTP: On ‘Verbose’ or ‘Extreme’ detail level, logfile now records all RCPT TOs that weren’t rejected by SpamPal as well as those that were.
- Installer was putting wrong default data in “auto-whitelist exclusions” options window – fixed.
- Auto-whitelist logging had become broken in 1.72i; fixed.
- transparent proxy:
- Fixed bug when filtered and unfiltered socket handles were used in the same WSPSelect call; was notably causing crashes in Thunderbird.
- System error state was being corrupted when creating socket; fixed.
- Was incorrectly trying to process returned fd_sets if WSPSelect returned an error; could potentially cause crashes. Fixed.
- Should no longer crash if you try to terminate the same connection twice.
- Played with connection-accepting code in attempt to solve crashes after hibernation.
- Crash Reporting:
- Disabled the “deadlock detection” as it frequently gave spurious results.
- Can now use spampal.mc file to include function names in crash reports.
- Now built using Microsoft Visual Studio 2003 toolkit.
|Operating systems||Windows 9x, Windows NT, Windows 2000, Windows XP|