...
To install it, perform the following steps:
| No Format |
|---|
wget httphttps://www.dcc-servers.net/dcc/source/dcc-dccproc.tar.Z
tar xfvz dcc-dccproc.tar.Z
cd dcc-dccproc-*2.3.167
./configure && make && make install
|
...
| No Format |
|---|
./configure \
--bindir=$(PREFIX)/bin \
--libexecdir=$(PREFIX)/lib/dcc \
--mandir=$(PREFIX)/man \
--homedir=/var/lib/dcc
|
It's recommended to run the persistent dccifd daemon for sites scanning more messages.
| No Format |
|---|
# create dcc user to run dccifd safely (Linux specific useradd arguments)
useradd -m -U -d /var/dcc -s /bin/sh dcc
# homedir needs to be owned by the user
chown -hR dcc:dcc /var/dcc
# start dccifd as dcc user (you could add this to /etc/rc.local for system startup, or see your OS manual)
su - -c '/var/dcc/libexec/dccifd' dcc
|
Finally call cdcc:
| No Format |
|---|
cdcc info
|
...
There should be *at least one*, preferably more than half a dozen, of the public DCC servers listed. If this is not the case, a likely cause is an interfering firewall (see below).
Note that MIMEDefang users may need to set the 'dcc_path' configuration setting, since MIMEDefang does not set a PATH by default. See also 'perldoc Mail::SpamAssassin::Conf'.
Also note that DCC requires that you open your firewall for DCC reply packets on UDP port 6277. DCC uses UDP packets when replying, which are blocked by most firewalls by default. As a result, it requires that you open your firewall for DCC reply packets on UDP port 6277. Here's sample firewall rules required:
| No Format |
|---|
allow udp local gt 1023 to remote 6277
allow udp remote 6277 to local gt 1023
|
If you're running a large site, processing upwards of tens of thousands of messages a day, the DCC maintainers have requested that you consider setting up your own DCC server as described in dccd(8), and arrange to peer with the rest of the public servers, to reduce their loadUsingDcc).
More info is at UsingDcc.