On Mon, 15 Jan 2007, Thomas Cameron wrote:
hI,
All -
I'm using Sendmail on RHEL 4 with SA and spamass-milter, clamav-milter
and milter-greylist. What is the best way for SpamAssassin to use DCC?
So far I've created an RPM with these configure options:
./configure \
--homedir=/var/dcc \
--bindir=/usr/bin \
--libexecdir=/usr/libexec \
--mandir=/usr/share/man \
--with-sendmail \
--with-cgibin=/var/www/cgi-bin \
--with-rundir=/var/run \
--disable-sys-inst \
--with-installroot=/var/tmp/%{name}-root
Once I created that RPM I set DCCUID=spam in /var/dcc/dcc_conf.
I also set DCCD_ENABLE=off since I am using a remote server.
I set GREY_ENABLE=off since I am using milter-greylist.
I set DCCM_ENABLE=off as I am not using a milter for DCC.
I set DCCIFD_ENABLE=yes as the DCC docs say If you are using
SpamAssassin, then you almost certainly should be using dccifd. Do I
need to do anything besides set use_dcc 1 in local.cf?
I copied /usr/libexec/rcDCC to /etc/rc.d/init.d and chkconfig'd it on.
Missing anything?
we are running SA/clamav-milter/razor2 and dccifd too. the only thing i
added, was my subnet to whitecommon. Prevents dcc tests of my trusted net,
from my understanding, reading the man pages :)
whitecommon:
ok ip xxx.xxx.0.0/16
one more thing was running dccifd as non-root user, adding:
# DCC user name
DCCUID=non-root
and disabling loging:
DCCM_LOGDIR=
all in dcc_conf.
once all is running, updating is way easy too, using:
$PREFIX/libexec/updatedcc
best regards,
Matthias
