Dear all,

I am trying to enable DCC support but as far as I can see no DCC_CHECK
is being involved. Your advise would be greatly appreciated.

FreeBSD 5.4-STABLE, qmail 1.03, SA 3.1.0 used with qmail-scanner 1.25,
dcc 1.3.16 - all installed from ports.

local.cf:

add_header all Status DCC _DCCB_ _DCCR_ "_YESNO_, hits=_HITS_
required=_REQD_ tests=_TESTS_ autolearn=_AUTOLEARN_ version=_VERSION_"

use_dcc 1
dcc_path /usr/local/bin/dccproc
dcc_home /usr/local/dcc
dcc_dccifd_path /usr/local/dcc/dccifd
dcc_options -x 0

I can see that dccifd is up and running:

netstat -l | grep dcc
c19df71c stream      0      0 c3641e70        0        0        0
/usr/local/dcc/dccifd

>From maillog:
Nov 22 10:38:55 mx02 dccifd[48890]: 1.3.16 listening to /usr/local/dcc/dccifd

"spamassassin -D --lint" also looks ok:

[48997] dbg: plugin: registering glue method for check_dcc
(Mail::SpamAssassin::Plugin::DCC=HASH(0x927c994))
[48997] dbg: dcc: dccifd is available: /usr/local/dcc/dccifd
[48997] dbg: info: entering helper-app run mode
[48997] dbg: dcc: dccifd got response: X-DCC-EATSERVER-Metrics:
mx02.manas.edu.kg 1166; Body=55750 Fuz1=506560 Fuz2=506555

As well as "cdcc info":

# 11/22/05 10:53:56 KGT  /usr/local/dcc/map
# Re-resolve names after 11:31:39  Check RTTs after 10:55:23
# 2075.82 ms threshold, 1849.41 ms average    12 total, 10 working servers
IPv6 off

dcc1.dcc-servers.net,-      RTT+1000 ms  anon
#  142.27.70.214,-                                 
CollegeOfNewCaledonia ID 1189
#      69% of 16 requests ok 2496.24+1000 ms RTT       805 ms queue wait
#  194.109.153.82,-                                             NIET ID 1080
#     100% of 11 requests ok 1075.83+1000 ms RTT        79 ms queue wait
#  208.201.249.233,-                                       sonic.net ID 1117
#      58% of 12 requests ok 3585.03+1000 ms RTT      1319 ms queue wait

dcc2.dcc-servers.net,-      RTT+1000 ms  anon
#  198.137.254.147,-                                           Misty ID 1170
#     100% of 12 requests ok 1127.19+1000 ms RTT       163 ms queue wait
#  209.157.153.22,-                                             meer ID 1086
#   protocol version 4
#      92% of 13 requests ok 3361.79+1000 ms RTT       313 ms queue wait

dcc3.dcc-servers.net,-      RTT+1000 ms  anon
#  137.208.8.26,-                                             wuwien ID 1290
#     100% of 19 requests ok 1185.02+1000 ms RTT       713 ms queue wait
#  208.201.249.232,-                                       sonic.net ID 1156
#      80% of 15 requests ok 2359.54+1000 ms RTT       517 ms queue wait

dcc4.dcc-servers.net,-      RTT+1000 ms  anon
#  137.118.60.88,-                                           neonova ID 1127
#   protocol version 4
#      not answering
#  203.147.165.193,-                                     MessageCare ID 1108
#   protocol version 4
#     100% of 13 requests ok 3233.43+1000 ms RTT       102 ms queue wait

dcc5.dcc-servers.net,-      RTT+1000 ms  anon
#  80.69.8.186,-                                                  MC ID 1128
#   protocol version 4
#      71% of 14 requests ok 3165.86+1000 ms RTT       105 ms queue wait
# *212.203.14.116,-                                        EATSERVER ID 1166
#      97% of 32 requests ok  923.30+1000 ms RTT        42 ms queue wait

127.0.0.1,-                 RTT-1000 ms  32768 1676696581x1182
#  127.0.0.1,-
#      not answering

################
# 11/22/05 10:53:56 KGT  GreyList /usr/local/dcc/map
# Re-resolve names after 12:04:51
# 1 total, 0 working servers

127.0.0.1,-                 Greylist 32768 1676696581x1182
#  127.0.0.1,6276
#      not answering

The problem is that I have never seen any DCC_CHECK performed. The
only suspicious thing I noticed is an error in maillog:

Nov 22 10:40:24 mx02 dccifd[48890]: write(MTA socket,69): Broken pipe

But I'm not quite sure whether it is relevant.

Thank you for your time!

Reply via email to