From: Murray S. Kucherawy <msk@se...> - 2007-10-01 14:58:26
There's only one person monitoring beta releases via SourceForge. As the
beta releases are highly informal, I don't always post about them here so
you might want to enable monitoring of that package on SourceForge if
you're keen to remain current.
Just for the sake of catching up, here's the whole 2.3.0 RELEASE_NOTES
entry so far:
Add "UseSSPDeny" configuration option which causes the filter
to reject messages which are determined to be suspicious
according to the new draft-ietf-dkim-ssp-01, and whose
sending domains advertise a recommended handling of "deny",
and whose SSP records are not in "test" mode.
Add "MaximumSignedBytes" configuration option limiting the number
of bytes of the message body to be signed.
Add "-t" command line option for reading an RFC2822-formatted
message from a named file and attempting to evaluate it.
Based on a patch from Kaspar Brand.
Add "TestPublicKeys" setting for instructing libdkim to read public
keys from a file, for use during automated testing.
Based on a patch from Jeff Barry.
When using _FFR_QUERY_CACHE, periodically report cache activity
Fix bug #25728: When "AutoRestart" is in use, try to remove the
socket (if it's a UNIX domain socket) prior to trying to
start the child.
LIBDKIM: Patch #SF1796687: Add DKIM_LIBFLAGS_ACCEPTV05 which causes
the library to accept signatures with version strings of
"0.5", i.e. those based on later versions of the DKIM draft
specification. This does not change any other part of
signature validation or canonicalization, only the version
string test. Suggested by Jim Fenton of Cisco.
LIBDKIM: When closing canonicalizations, flush the temporary files
rather than closing them so that things like dkim_reportinfo()
return useful descriptors. Close the temporary files in
dkim_canon_free() only. Problem noted by Jeff Barry.
LIBDKIM: Fix variable argument processing by merging dkim_error()
and dkim_verror(). The previous code was causing
segmentation faults on selected operating systems.
Activate the following FFRs:
I only have a couple of patch contributions to consider now before moving
out of the beta phase, so I'm hoping to post the release Wednesday. The
outstanding bugs have been resolved to my satisfaction, at least for now.
Get latest updates about Open Source Projects, Conferences and News.