CDCC info shows "not answering"...

Gary V lists@johnmecham.com
Wed Nov 8 20:49:59 UTC 2006


Ken wrote:

>>> 
>>> When running cdcc 'info', everything looks as I expected except at
> the 
>>> very end where I see:
>>> 
>>> ################
>>> # 11/07/06 09:15:00 EST  GreyList /var/dcc/map # Re-resolve names 
>>> after
>>> 10:56:24 # 1 total, 0 working servers # skipping asking Greylist 
>>> server
>>> 128 seconds more
>>> 
>>> 127.0.0.1,-                 Greylist 32768 2187038903x280
>>> #  127.0.0.1,6276                                  
>>> #      not answering
>>> 
>>> Does this indicate a problem?  If so, how do I resolve it?

>> Ludger replied on Nov 11 2006:
>>
>> This shows that you do not have a working greylist server running on
> your local host.  If you do not want to 
>> run a greylist server you may edit /var/dcc/map.txt and uncomment the
> line 127.0.0.1 ....
>> Rebuild the map file with cdcc "load map.txt"    
 
> Thanks very much for the response.

> That line in map.txt was already uncommented (the line didn't begin with
> "#").  So I tried uncommented and commented, using /usr/bin/cdcc 'load
> /var/dcc/map.txt' to rebuild the map file.  The map file is getting
> rebuilt (according to the timestamp), but doesn't change anything as
> cdcc 'info' still yields:

> ----<snip>----
> ################
> # 11/08/06 13:56:17 EST  GreyList /var/dcc/map
> # Re-resolve names after 15:50:37  
> # 1 total, 0 working servers
> # skipping asking Greylist server 128 seconds more

> 127.0.0.1,-                 Greylist 32768 2187038903x280
> #  127.0.0.1,6276                                  
> #      not answering



> Here's my map.txt:

> # Sample DCC client information
> #   See cdcc(8) about loading this file into the memory mapped client
> file,
> #   /var/dcc/map, with the "load" command.  When used for that purpose,
> #   it must not be publicly readable.

> #   This file is otherwise only documentation for the mapped client
> file.
> #   It is handy to regularly update it with a command like
#       `cdcc info >> map.txt` and archive it with RCS or SCCS.
> #   Note that command must be run as the dcc user or the passwords will
> not be
> #   captured.

> # public DCC servers
> #       REMOVE THESE LINES from any spam appliance or filter that you
> sell.
> #       It is wrong to take and sell the human system administration
> work
> #       of the operators of the public DCC servers.
> dcc1.dcc-servers.net    RTT+1000 ms     anon
> dcc2.dcc-servers.net    RTT+1000 ms     anon
> dcc3.dcc-servers.net    RTT+1000 ms     anon
> dcc4.dcc-servers.net    RTT+1000 ms     anon
> dcc5.dcc-servers.net    RTT+1000 ms     anon

> # local DCC server
> # 127.0.0.1   RTT-1000 ms    32768 2187038903x280

> # local greylist server
> # 127.0.0.1   GREYLIST     32768 2187038903x280


> So what am I missing here?

> Thanks again!

Try:

cdcc "delete 127.0.0.1 Greylist"

Gary V




More information about the DCC mailing list

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