Eergisteren heeft James Farmer een nieuwe bètarelease van SpamPal uitgebracht. Het versienummer is aanbeland bij 1.73g en het programma kan worden gedownload als installer of in zip-formaat. SpamPal is een anti-spamprogramma voor Windows en zit als het ware tussen de e-mailclient en de mailbox in, en is bedoeld om spam te identificeren en als zodanig te markeren. Deze markering kan dan vervolgens in je favoriete e-mailprogramma worden gebruikt om een filter aan te maken die deze e-mail bijvoorbeeld in een aparte folder zet of direct weggooit. In deze release diverse problemen verholpen, waaronder een in de transparent proxy die Mozilla Thunderbird regelmatig lieten vastlopen. Het volledige changelog ziet er als volgt uit:
Changes in 1.73g (Beta Release)[break]
- 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 occaisionally. (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 crases 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.
:strip_exif()/u/2537/avatar_tweakers.gif?f=community){kind=avatar}
:strip_icc():strip_exif()/u/72348/avatar-pic-beach-xj6-70-53-compr.jpg?f=community){kind=avatar}
/u/48718/crop619e5ed546e66_cropped.png?f=community){kind=small}