[pkgsrc/trunk]: pkgsrc/mail/spamdyke Update to 4.0.7. From the changelog:

[schmonz <schmonz%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/f3f635a1437e
branches:  trunk
changeset: 548580:f3f635a1437e
user:      schmonz <schmonz%pkgsrc.org@localhost>
date:      Sat Oct 18 04:51:01 2008 +0000

description:
Update to 4.0.7. From the changelog:

VERSION 4.0.7: 10/17/2008
  Changed Makefile.in to compile configuration.c in two steps: first use gcc
    to produce the preprocessed source, then use gcc to compile it.  For some
    reason, gcc crashes on FreeBSD 6.0 when the file is compiled in one step.
    Thanks to K. Shantanu for reporting this one and Felix Buenemann for
    suggesting the fix.

VERSION 4.0.6: 10/16/2008
  Fixed a problem in examine_ip_in_rdns_keyword_entry() that was not correctly
    terminating the end of the keyword buffer, causing strstr() to search too
    far, leading to false negatives (and potentially segmentation faults).
    Thanks to Erald Troja for reporting this one.
  Fixed another problem in middleman() that was not correctly replacing _all_
    of qmail's AUTH advertisements when the "smtp-auth-level" option is
    "always" or "always-encrypted".  Thanks to Youri Kravatsky for reporting
    this one (again).
  Fixed the fix to a bug in nihdns_query() that was setting
    return_target_name_index to 0 in all cases.  This was causing log messages
    to print the first RBL/RHSBL name instead of the one that actually matched.
    Thanks to Arthur Girardi for reporting this one (again).
  Reverted a change from 4.0.5 -- removing the usable_buf_input flag from
    middleman() meant could only tell if there was input in the buffer, not if
    any of it was actually usable.  If the remote server delays sending its
    data for any reason, middleman() will loop rapidly to continually check if
    its buffered data can be sent to qmail.  Removing the flag meant spamdyke
    was consuming 100% CPU while receiving messages with large attachments.
    Thanks to Paulo Henrique Fonseca for reporting this one.
  Added the "cputime" program to the "tests" folder to measure the CPU time
    used by a process.  Neither the shell "time" command nor the POSIX "time"
    command seem to do that.
  Changed sendrecv to always wait() for its child processes so CPU accounting
    will be performed correctly.
  Fixed check_rhsbl() to correctly return the name of the matching RHSBL instead
    of an index that could be beyond the end of the array.
  Changed the values of LOG_USE_CONFIG_TEST, LOG_USE_STDERR and LOG_USE_SYSLOG
    to make none of them equal to 0.  Because the "log-target" option is a
    CONFIG_TYPE_NAME_MULTIPLE option, it is set to 0 until the command line and
    all configuration files are parsed.  When LOG_USE_CONFIG_TEST is 0, the
    progress messages from process_config_file() are sent to stderr until the
    configuration file is completely loaded.  For Plesk users, xinetd sends
    stderr to the network connection, so the remote server gets the output.
    Thanks to Arthur Girdari for reporting this one and helping track it down.

diffstat:

 mail/spamdyke/Makefile |  4 ++--
 mail/spamdyke/distinfo |  8 ++++----
 2 files changed, 6 insertions(+), 6 deletions(-)

diffs (27 lines):

diff -r bc56a79cdc4f -r f3f635a1437e mail/spamdyke/Makefile
--- a/mail/spamdyke/Makefile    Sat Oct 18 01:35:25 2008 +0000
+++ b/mail/spamdyke/Makefile    Sat Oct 18 04:51:01 2008 +0000
@@ -1,7 +1,7 @@
-# $NetBSD: Makefile,v 1.19 2008/10/13 15:24:37 schmonz Exp $
+# $NetBSD: Makefile,v 1.20 2008/10/18 04:51:01 schmonz Exp $
 #
 
-DISTNAME=      spamdyke-4.0.5
+DISTNAME=      spamdyke-4.0.7
 CATEGORIES=    mail
 MASTER_SITES=  ${HOMEPAGE}releases/
 EXTRACT_SUFX=  .tgz
diff -r bc56a79cdc4f -r f3f635a1437e mail/spamdyke/distinfo
--- a/mail/spamdyke/distinfo    Sat Oct 18 01:35:25 2008 +0000
+++ b/mail/spamdyke/distinfo    Sat Oct 18 04:51:01 2008 +0000
@@ -1,6 +1,6 @@
-$NetBSD: distinfo,v 1.19 2008/10/13 15:24:37 schmonz Exp $
+$NetBSD: distinfo,v 1.20 2008/10/18 04:51:01 schmonz Exp $
 
-SHA1 (spamdyke-4.0.5.tgz) = 21b19d8904a8065289a535f494da3d7ed1a48ae8
-RMD160 (spamdyke-4.0.5.tgz) = db3877087241f46fa64261d19091c06f46c9aebe
-Size (spamdyke-4.0.5.tgz) = 447509 bytes
+SHA1 (spamdyke-4.0.7.tgz) = 64b6771e5e22490bb80a3ceb43b01508f8637696
+RMD160 (spamdyke-4.0.7.tgz) = cefafb2cfac1f20ba150d636bbd1c5ddeb052b98
+Size (spamdyke-4.0.7.tgz) = 451491 bytes
 SHA1 (patch-aa) = bb988fc5cad08f8e4e05a0aa67d767c48f975955