Use of DCC Clarification

[Gerry Doris]

> 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 and
you're going to add the dcc_path statement?  Both of those seem to be
required to make DCC work.

Gerry