DCC version 1.3.43/2.3.43 released

Vernon Schryver vjs@calcite.rhyolite.com
Mon Nov 13 20:54:51 UTC 2006

Version 1.3.43 of the DCC source is in
http://www.dcc-servers.net/dcc/source/dcc.tar.Z  and

Commercial version 2.3.43 of the DCC Reputation code is in the usual place.
The CHANGES file starts with:
    Make "option forced-discard-nok" in /var/dcc/whiteclnt the default for
	dccm as well as dccifd in proxy mode.
    Add whiteclnt type of IP address entry "submit".
	It is intended to be applied to the IP addresses of SMTP submission
	clients such as web browsers that cannot tolerate 4yz temporary
	rejections of mail, but that cannot be trusted to not send spam.
    Let body and reputation checksum thresholds be set in the global and
	per-user whiteclnt files.  "Never" is a valid threshold and turns
	off rejections for a checksum.
    Overhaul proof of concept per-user whiteclnt CGI scripts to handle
	per-user checksum thresholds.
    Rationalize /var/dcc/libexec/dcc-stats-graph -tTITLE
    Fix bugs with -eNEVER and -Enever in dbclean.
    Add "submit" to "mx" and "mxdcc" values for IP addresses whiteclnt files
	to mark SMTP clients that are submitting new messages and that
	do not understand 4yz rejections for individual recipients.
    Fix dccifd crash on bogus long recipient names diagnosed by Tomasz Potega.
    /var/dcc/libexec/fetchblack is not as noisy when the sources of the
	public DCC server blacklist are down for long periods.
    Limit the database window to less than 2 GBytes on all 32-bit systems
	including Solaris.  Previous versions assumed that Solaris would
	do the right thing if it allowed large files.
    Fix bugs in the "skipping asking DCC server" mechanism that made it
	too forgiving.
    Remove the `dccd -t` thresholds in favor of simple constants.
    Dccm, dccifd, and dccproc now emit X-DCC headers for locally white-
	and blacklisted messages even when no DCC server responds.
    Automatically compensate for incompatibility in newer versions of
    Prefer poll() to select() on Linux.
    Increase the computed limit on `dccm -j` by not dedicating two FDs
	to each thread for per-user log files but instead doing some locking.

/var/dcc/libexec/updatedcc should automagically fetch, build, and install
this version, unless you have installed a version of Linux with the
broken default `sort` collating sequence since last upgrading.
If so, an easy way to get the old updatedcc script working is to delete
the entire /var/dcc/build/dcc directory before running updatedcc.

Vernon Schryver    vjs@rhyolite.com

More information about the DCC mailing list

Contact vjs@rhyolite.com by mail or use the form.