DCC config and SA lint complaints

[Jeff A. Earickson]

I finally hacked around this issue by having two copies of
spam.assassin.prefs.conf in /opt/MailScanner/etc, one for
regular MailScanner/SA work  (with the entries in it so DCC
uses dccifd and the socket, not dccproc), and one copy without
the DCC entries, for use in the Rules_du_jour lint action:

SA_LINT="/opt/perl5/bin/spamassassin -p 
/opt/MailScanner/etc/spam.assassin.prefs.conf.nodcc --lint"

This keeps the Rules_du_Jour wrapper script from failing because
the lint on the normal perfs file fails.  Sheesh.

Jeff Earickson
Colby College

On Fri, 7 Jul 2006, Aaron K. Moore wrote:

> Date: Fri, 7 Jul 2006 09:01:20 -0400
> From: Aaron K. Moore <amoore at dekalbmemorial.com>
> Reply-To: MailScanner discussion <mailscanner at lists.mailscanner.info>
> To: MailScanner discussion <mailscanner at lists.mailscanner.info>
> Subject: RE: DCC config and SA lint complaints
> 
> Arthur Sherman wrote:
>> It should be in MailScanner.conf, I believe:
>> #use_dcc
>>
>> As for the path...
>> Funny, I had it in the different order and it worked with no problem
>> (pls mention diff. path!)
>>
>> dcc_home  /var/dcc
>> dcc_path  /var/dcc/bin/dccproc
>>
>
> You might want to look into running dccifd instead of using dccproc.
>
>> From the dccifd manpage:
>
> "Dccifd is a daemon intended to connect spam filters such as SpamAssasin
> and mail transfer agents (MTAs) other than sendmail to DCC servers.  The
> MTA or filter dccifd which in turn reports related checksums to the
> near-
> est DCC server.  DCCIFD then adds an X-DCC SMTP header line to the mes-
> sage.  The MTA is told to reject the message if it is unsolicited bulk."
>
> I switched to using this method with SpamAssassin a couple of years ago.
> It greatly reduced the load I was seeing from all of the forks to call
> dccproc.
>
> I have set the following items in the SpamAssassin config file.
> use_dcc 1
> dcc_home /var/dcc
> dcc_path /var/dcc
> dcc_timeout 15
>
> Depending on your setup you might also need to set dcc_dccifd_path.
>
> dcc_dccifd_path STRING
>
> This option tells SpamAssassin specifically where to find the dccifd
> socket. If dcc_dccifd_path is not specified, it will default to looking
> in dcc_home If a dccifd socket is found, it will use it instead of
> dccproc.
>
> -- 
> Aaron Kent Moore
> Information Technology Services
> DeKalb Memorial Hospital, Inc.
> Auburn, IN
> E-mail:  amoore at dekalbmemorial.com
> -- 
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
> Before posting, read http://wiki.mailscanner.info/posting
>
> Support MailScanner development - buy the book off the website!
>