BTW, I further tested the config by manually invoking both spamassassin
and spamc, both generate the X-Spam-DCC header -- including invoking
spamc with a uid of exim, as should be happening with the mailer.
(Spamd runs under its own, non-privileged uid, so the invoking uid
shouldn't matter, an
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..
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
"Smart,Dan" writes:
>I suggest that instructions to get dccifd running should be included in
>INSTALL...
Dan, any chance you could add a page to the wiki?
http://wiki.SpamAssassin.org/
- --j.
>Compile the dcc as directed in INSTALL doc.
>Get dccpro
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_L
