DCC version 1.2.30

Version 1.2.30 of the DCC source is in
http://www.dcc-servers.net/dcc/source/dccd.tar.Z  and
http://www.rhyolite.com/anti-spam/dcc/source/dccd.tar.Z

The point of this release is to help greylisting.  Users can now
be told:
  If greylisting doesn't work for your, you can turn it off.
  You can also advise the greylist system about legitimate senders.

That last is based on the changes to dccd, dccsight, and the CGI
scripts.  That feature will speed mail from ISPs like Earthlink that
shuffle outoing mail among SMTP clients, but its main value is political.
People really hate not feeling in control.  Letting users opt-out of
greylisting entirely or mark legitimate senders for faster future
delivery will make many people more comfortable with greylisting.


DCC servers on Solaris and FreeBSD are significantly faster in recent
releases.  Just installing a recent version on FreeBSD helps dccd.
Adding -F to DBCLEAN_ARGS in /var/dcc/dcc_conf significantly speeds
up dbclean on many Solaris systems.   (I recommend *NOT* using -F in
DCCD_ARGS or on systems other than Solaris.)


http://www.dcc-servers.net/dcc/CHANGES starts with:

    Let `dccd -C` take arguments for dbclean, so that the following line
	in dcc_conf works:
		DCCD_ARGS="'-C$DCC_LIBEXEC/dbclean -F'"
    Make pthread_detach() failures in dccifd non-fatal.
    Add mechanism to cgi-bin/list-msg to whitelist-for-greylisting
	(sender,IP-address,recipient) checksums.  This mechanism
	requires that the 1.2.30 versions of dccd and dccsight be
	installed.
    Change dccifd to record the message headers in the log file even when
	the MTA fails to provide the message body.

If you have previously installed 1.2.12 or newer, then
/var/dcc/libexec/updatedcc should make it easy to fetch, build, and
install this version.
The automatically generated /var/dcc/dcc_conf-new might make it easy
to generate a new dcc_conf file for turning on greylisting.


Vernon Schryver    vjs@rhyolite.com