DCC has been one of the more difficult things for me to setup, but I like it a lot.
You need to run only one of the dcc programs, depending on your needs. Run dccd if you want to be a DCC server and you have registered on the dcc network. Or run as an anonymous connection either dccm for a sendmail milter, dccifd (this is what SA can use directly) or dccproc to run dcc check outside of SA and from procmail only. You firewall needs UDP/6277 send-receive. If cdcc info returns 'not answering', the firewall is blocking the dcc traffic. Out of the stock dcc map file, you should typically see only localhost listed as 'not answering'. I have recently seen a good document for this setup and I think that it was in the MIMEDefang FAQ. I have run dcc as a milter, but I like the integration with SA better. I would try this first. dccifd should be pointed to in your SA local.cf file with the following type of information. Change this as desired. use_dcc 1 dcc_path /opt/csw/var/dcc/ dcc_home /opt/csw/var/dcc/ dcc_dccifd_path /opt/csw/var/dcc/dccifd # dcc_body_max # dcc_fuz1_max # dcc_fuz2_max dcc_add_header 0 Alex Moore -- On Tue, 9 Dec 2003 09:04:42 -0500 stan <[EMAIL PROTECTED]> wrote: > Hi, I'm in the process of implementing Spamassain on my Debain machine. > > I've installed itand got it working in a fairly simple fashion, and now I'm > trying to ad in some options. I've got Razor working, and my next goal os > to get DCC working. I was unable to locate a Debian package for this, so I > built it from the latest sources. > > At the moment I seem to be able to _report_ spam to them, but I don't > _think_ Spamassaian is able to use it to check incoming mail. > > I've modified my firewall configuration (on an OpenBSD machien) so that I > have port 6277 open for UDP packets coming in, but when I run cdcc info, I > get the following: > > > Script started on Tue Dec 9 08:57:50 2003 > [EMAIL PROTECTED]:~$ cdcc infog > # 12/09/03 08:57:58 EST /var/dcc/mapg > # Re-resolve names after 10:53:05 g > # 12 total, 0 working serversg > IPv6 offg > g > dcc1.dcc-servers.net,- RTT+0 ms anong > # 208.201.249.233,- g > # not answeringg > # 212.95.66.23,- g > # not answeringg > # 216.240.97.63,- g > # not answeringg > g > dcc2.dcc-servers.net,- RTT+0 ms anong > # 206.169.162.65,- g > # not answeringg > # 208.201.249.232,- g > # not answeringg > g > dcc3.dcc-servers.net,- RTT+0 ms anong > # 198.137.254.71,- g > # not answeringg > # 203.147.165.193,- g > # not answeringg > g > dcc4.dcc-servers.net,- RTT+0 ms anong > # 207.195.195.223,- g > # not answeringg > # 212.69.217.26,- g > # not answeringg > g > dcc5.dcc-servers.net,- RTT+0 ms anong > # 153.19.44.252,- g > # not answeringg > # 194.85.132.210,- g > # not answeringg > g > 127.0.0.1,- RTT-1000 ms 32768 g > # 127.0.0.1,- g > # not answeringg > g > ################g > # 12/09/03 08:57:58 EST GreyList /var/dcc/mapg > # Re-resolve names after 10:55:56 g > # 1 total, 0 working serversg > g > 127.0.0.1,- Greylist 32768 g > # 127.0.0.1,- g > # not answeringg > g > > So, to test my firewall config I used traceroute. > > [EMAIL PROTECTED]:~$ traceroute -p 6277 dcc1.dcc-servers.netg > traceroute: Warning: dcc1.dcc-servers.net has multiple addresses; using > 208.201.249.232g > traceroute to dcc.dcc-servers.net (208.201.249.232), 30 hops max, 38 byte packetsg > 1 koala (205.159.77.234) 1.053 ms 0.757 ms 3.248 msg > 2 10.116.72.1 (10.116.72.1) 9.190 ms 22.048 ms 33.081 msg > 3 172.30.75.81 (172.30.75.81) 9.644 ms 9.809 ms 8.370 msg > 4 172.30.75.122 (172.30.75.122) 8.596 ms 27.574 ms 9.224 msg > 5 12.124.58.77 (12.124.58.77) 19.150 ms 18.641 ms 20.646 msg > 6 gbr5-p80.attga.ip.att.net (12.123.21.74) 21.172 ms 32.190 ms 19.746 msg > 7 tbr2-p013501.attga.ip.att.net (12.122.12.41) 21.487 ms 27.284 ms 24.384 msg > 8 ggr1-p370.attga.ip.att.net (12.123.20.253) 21.536 ms 21.056 ms 20.245 msg > 9 att-gw.ny.cw.net (192.205.32.118) 21.074 ms 21.752 ms 20.048 msg > 10 dcr1-loopback.SantaClara.cw.net (208.172.146.99) 82.517 ms 82.504 ms 98.134 > msg > 11 bpr1-so-0-0-0.SanJoseEquinix.cw.net (208.173.54.65) 81.197 ms 79.956 ms > 106.910 msg > 12 208.173.54.46 (208.173.54.46) 77.201 ms 76.175 ms 76.272 msg > 13 fast5-0-0.border.sr.sonic.net (64.142.0.13) 83.196 ms 512.588 ms 216.541 msg > 14 fast0-1.dist2-1.sr.sonic.net (208.201.224.160) 84.227 ms 81.727 ms 89.809 msg > 15 eth0.d.spam.sonic.net (208.201.249.232) 108.510 ms 85.306 ms 88.993 msg > [EMAIL PROTECTED]:~$ > Script done on Tue Dec 9 08:58:31 2003 > > And this looks OK to me. > > One thing I _have not_ done is atrt any of the daemons running, because I > did not think I needed them jsut to use DCC with Spamassain. is this > incorect? If so, what daemon do I need to have running? If not, what other > things can I check? > > Thanks. > > And thatks for this prohect, it's going to make my life _LOTSL more > pleasent! > > -- > "They that would give up essential liberty for temporary safety deserve > neither liberty nor safety." > -- Benjamin Franklin > > > ------------------------------------------------------- > This SF.net email is sponsored by: IBM Linux Tutorials. > Become an expert in LINUX or just sharpen your skills. Sign up for IBM's > Free Linux Tutorials. Learn everything from the bash shell to sys admin. > Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click > _______________________________________________ > Spamassassin-talk mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/spamassassin-talk ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
