spamdyke version 4.0.5 is now available:
        http://www.spamdyke.org/

This version fixes a number of bugs:
        If the idle timeout is not configured, it is now set to 20 minutes 
after qmail exits to prevent never-ending spamdyke processing.  Thanks to 
Matthew Kettlewell for reporting this one.
        Fixed the AUTH advertisements to display correctly when 
"smtp-auth-level" is "always" or "always-encrypted".  Thanks to Youri Kravatsky 
for reporting this one.
        Fixed a sequencing error that would cause qmail to exit prematurely, 
even if valid recipients could still possibly be given.  Thanks to David 
Stiller for reporting this one.
        Fixed the handling of unencoded null characters in messages 
(technically not legal) so spamdyke does become confused and timeout.  Thanks 
to Arthur Girardi for reporting this one.
        Fixed an issue in the DNS query code that was setting array indexes 
beyond the end of the array, resulting in garbage log messages and segmentation 
faults.  Thanks to Arthur Girardi for reporting this one.
        Fixed verbose logging in the RHSBL filter to print the correct log 
message.  Thanks to Arthur Girardi for reporting this one.
        Rewrote the address parser to correctly handle strange/invalid email 
addresses.  Thanks to Erald Troja for reporting this one.
        Fixed a serious error in the code that loads array values from files 
that was returning pointers to unallocated memory, causing segmentation faults. 
 Many, many thanks to David Stiller for reporting this one and providing tons 
of help to nail it down.
        Fixed a serious error that was attempting to move data by dereferencing 
the NULL address when the remote server disconnected unexpectedly, causing 
segmentation faults.  Many, many thanks to David Stiller for reporting this one 
and providing tons of help to nail it down.

Version 4.x is NOT backwards compatible with 3.x; be sure to read the 
documentation before upgrading.

Version 4.0.5 is backwards-compatible with version 4.0.4; simply replacing the 
old binary with the new one should be safe.

-- Sam Clippinger

_______________________________________________
spamdyke-release mailing list
spamdyke-release@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-release

Reply via email to