dccproc -V option gives broken pipe

Hi Mr. Vernon Schryver
>
> A few hundred other people are using SpamAssassin with dccproc.  Because
> the combination is working for them, they cannot be using -V.
>
I replaced /usr/local/bin/dccproc by a symlink to /bin/cat and ran
spamassassin again.
This is the error i get:
debug: DCC is available: dccproc: invalid option -- V
 Try `dccproc --help' for more information.

Broken pipe

This would suggest that it is run with the -V parameter. As 'cat -V' gives
the same kind of error
The normal output is
debug: DCC is available: 1.1.6 -> i guess this is output from the -V
parameter

>
> That suggests that you are using a DCC client-ID that the DCC servers
> do not like.  Judging from logs on some of the servers whose IP
> addresses are in dcc.dcc-servers.net, you are using a client-ID of 0.
> That is an invalid client-ID and suggests that your /var/dcc/map file
> is corrupt.  Do you have and clues how that might have happened?
> Recent versions of the DCC source tarball generate and install a sample
> /var/dcc/map file.  That process works find on RedHat 5.2.
>
> If my guess that your /var/dcc/map file is broken, then it can
> be fixed by  `cdcc "delete dcc.dcc-servers.net; add dcc.dcc-servers.net"`
>
I replaced the map file by
cdcc "load map.txt"

[root@linuxnol:/var/dcc]#cdcc info
# 07/19/02 10:40:26 CEST  /var/dcc/map
# Will re-resolve names after 01:00:00
#  0 total addresses  0 working
IPv6 off

dcc.dcc-servers.net,-      anon

localhost,-                anon

But cdcc stats still gives the same output.
[root@linuxnol:~]#cdcc stats
badly signed NOP response from dcc.dcc-servers.net (195.74.212.70,6277)
badly signed NOP response from dcc.dcc-servers.net (207.8.219.218,6277)
badly signed NOP response from dcc.dcc-servers.net (192.188.61.3,6277)
badly signed NOP response from dcc.dcc-servers.net (206.169.162.65,6277)
badly signed NOP response from dcc.dcc-servers.net (216.158.54.132,6277)
badly signed NOP response from dcc.dcc-servers.net (195.74.212.70,6277)
badly signed NOP response from dcc.dcc-servers.net (207.8.219.218,6277)
badly signed NOP response from dcc.dcc-servers.net (192.188.61.3,6277)
badly signed NOP response from dcc.dcc-servers.net (206.169.162.65,6277)
badly signed NOP response from dcc.dcc-servers.net (216.158.54.132,6277)
badly signed NOP response from dcc.dcc-servers.net (195.74.212.70,6277)
badly signed NOP response from dcc.dcc-servers.net (207.8.219.218,6277)
badly signed NOP response from dcc.dcc-servers.net (192.188.61.3,6277)
badly signed NOP response from dcc.dcc-servers.net (206.169.162.65,6277)
badly signed NOP response from dcc.dcc-servers.net (216.158.54.132,6277)
badly signed NOP response from dcc.dcc-servers.net (195.74.212.70,6277)
badly signed NOP response from dcc.dcc-servers.net (207.8.219.218,6277)
badly signed NOP response from dcc.dcc-servers.net (192.188.61.3,6277)
badly signed NOP response from dcc.dcc-servers.net (206.169.162.65,6277)
badly signed NOP response from dcc.dcc-servers.net (216.158.54.132,6277)
DCC servers dcc.dcc-servers.net localhost at 192.188.61.3 195.74.212.70
206.169.162.65 ... not responding
 ?

The solution can not be far away. Thanks for any feedback.
Joeri