Use of DCC Clarification

[Julian Field]

Sorted.
Will all be set in the next release.

At 18:47 08/05/2003, you wrote:
>Hard for me to say.  Creating a symlink from /usr/local/bin/dccproc to
>/usr/bin/dccproc makes it all work.  I guess it depends on how MailScanner
>makes
>the call.  I'm no programmer, so don't make me lie to you :)
>
>Mike
>
>
> > -----Original Message-----
> > From: MailScanner mailing list
> > [mailto:MAILSCANNER at JISCMAIL.AC.UK] On Behalf Of Julian Field
> > Sent: Thursday, May 08, 2003 12:33 PM
> > To: MAILSCANNER at JISCMAIL.AC.UK
> > Subject: Re: Use of DCC Clarification
> >
> >
> > At 18:20 08/05/2003, you wrote:
> > >/usr/local/bin on my systems
> >
> > But should the entry read
> >          dcc_path /usr/local/bin
> > or
> >          dcc_path /usr/local/bin/dccproc
> > ?
> >
> >
> > >-----Original Message-----
> > >From: MailScanner mailing list
> > [mailto:MAILSCANNER at JISCMAIL.AC.UK] On
> > >Behalf Of Julian Field
> > >Sent: Thursday, May 08, 2003 12:19 PM
> > >To: MAILSCANNER at JISCMAIL.AC.UK
> > >Subject: Re: Use of DCC Clarification
> > >
> > >
> > >At 17:37 08/05/2003, Gerry Doris wrote:
> > > > > At 23:31 07/05/2003, you wrote:
> > > > >>On Wed, 7 May 2003, Julian Field wrote:
> > > > >> > Can you just do a quick test for me, and set
> > dcc_path to a path
> > > > >> > that
> > > > >> > *doesn't* exist please?
> > > > >> >
> > > > >> > I want to make sure that no error messages are
> > logged anywhere,
> > > > >> > as otherwise the logging is going to get very noisy
> > if it gets
> > > > >> > an error
> > > > >> for
> > > > >> > every message.
> > > > >> > --
> > > > >> > Julian Field
> > > > >> > www.MailScanner.info
> > > > >> > MailScanner thanks transtec Computers for their support
> > > > >>
> > > > >>I couldn't find any sign of an error message with an incorrect
> > > > >>dcc_path parameter.  There's no messages to root, nothing in
> > > > >>/var/log/messages or /var/log/maillog and no mention in the
> > > > >>headers. DCC checking just  doesn't happen.
> > > > >
> > > > > I have changed the spam.assassin.prefs.conf file for the next
> > > > > release so that this rule is no longer set to 0.
> > > > > --
> > > > > Julian Field
> > > > > www.MailScanner.info
> > > > > MailScanner thanks transtec Computers for their support
> > > >
> > > >Just so we're clear on this...
> > > >
> > > >You're going to change the existing DCC rule so that it
> > isn't set to
> > > >0
> > >
> > >Done.
> > >
> > > >  and
> > > >you're going to add the dcc_path statement?  Both of those
> > seem to be
> > > >required to make DCC work.
> > >
> > >Haven't done that yet.
> > >What should I set it to for a normal dcc installation? (I
> > don't use dcc
> > >myself
> > >yet)
> > >
> > >
> > >--
> > >Julian Field
> > >www.MailScanner.info
> > >Professional Support Services at www.MailScanner.biz
> > MailScanner thanks
> > >transtec Computers for their support
> >
> > --
> > Julian Field
> > www.MailScanner.info
> > Professional Support Services at www.MailScanner.biz
> > MailScanner thanks transtec Computers for their support
> >

--
Julian Field
www.MailScanner.info
Professional Support Services at www.MailScanner.biz
MailScanner thanks transtec Computers for their support