SA 3.1.3 + DCC 1.3.

Jeff Mincy
Fri Jun 23 01:38:06 UTC 2006

On Thu, 22 Jun 2006, wrote:

>> From: Jeff Mincy 
>> The empty string is kind of a bummer.   The empty string is also
>> returned for various problems.
>> Would it be possible to return a different string for whitelisted
>> messages?  Maybe something like:
>>   X-FOO-Metrics: 1234; Body=ok Fuz1=ok Fuz2=ok; whitelisted
> Which empty string?

The empty string result that you get for whitelisted messages.
For example with dccproc:
   bash% result=`/usr/local/bin/dccproc -H -S mail_host -w /var/dcc/whiteclnt -R < /home/jeff/mail/backup/msg._KuO`
   bash% echo "'$result'"
   bash% result=`/usr/local/bin/dccproc -H -R < /home/jeff/mail/backup/msg._KuO`
   bash% echo "'$result'"
   'X-DCC-INFN-TO-Metrics: 1233; Body=1 Fuz1=1

I have also seen empty string results for timeouts and also crashes
when using dccproc (eg like the crash fixed in 1.3.25).  I want
locally whitelisted messages to have a different result than timeouts
and crashes.

> Why should the DCC client say "whitelisted" when it already says "ok",
> "ok", and "ok"?  Can't whatever is trying to parse the X-DCC line
> look for "ok" as easily as "whitelisted"?

The ok/ok/ok would be so that any program that reads the existing
result string, such as SpamAssassin, will work without modification.

The explicit 'whitelist' would be useful for looking at log files.  I
save the dcc result in the X-Spam-DCC header.  For the 349 results,
215 had a Body count, 134(349-215) DCC results were blank, and 126 had
a many count.

    bash% fgrep X-Spam-DCC mail/logs/log_dev_null | wc -l 
    bash% fgrep X-Spam-DCC mail/logs/log_dev_null | fgrep Body | wc -l
    bash% fgrep X-Spam-DCC mail/logs/log_dev_null | fgrep many | wc -l

An explicit 'whitelist' result would tell me which messages were
locally whitelisted and which messages went out to the DCC servers.


More information about the DCC mailing list

Contact by mail or use the form.