I just got a dcc client up and running over the weekend -- enjoyed a similar process. The doc definitely leaves something to be desired. I'm looking forward to bringing up a server, now. ;)

Tried adding the header you suggested, but I get nothing. No errors from spamassassin --lint, either....


Smart,Dan wrote:


I suggest that instructions to get dccifd running should be included in
INSTALL...

Compile the dcc as directed in INSTALL doc.
Get dccproc running first as described in INSTALL doc.

To use dccifd in Spamassassin fix the dcc_conf and add path settings.

In /var/dcc/dcc_conf:
DCCM_ENABLE=off
DCCM_LOGDIR=
DCCM_WHITECLNT=
DCCM_USERDIRS=
DCCM_LOG_AT=
DCCM_REJECT_AT=
DCCD_ENABLE=off
DCCIFD_ENABLE=on

In /etc/mail/spamassassing/local.cf:
## DCC header not needed, but very informative...
add_header all DCC _DCCB_: _DCCR_
## dcc_path needed for dccproc
dcc_path /usr/local/bin/dccproc
## Either (or both) of following used to find dccifd
dcc_dccifd_path /var/dcc/dccifd
dcc_home /var/dcc
## Make sure you are using dcc
use_dcc 1

Load /var/dcc/libexec/start_dccifd in rc.local (or use rcDCC) before running

Spamd. (Order may not matter, just what dcc doc said)







------------------------------------------------------- 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

Reply via email to