Re: DCC and spamassassin -r

2005-09-19 Thread Nix
On Sun, 18 Sep 2005, Graham Murray stipulated:
 The DCC checkers, dccproc and dccifd, not only check the mail but also
 increment the 'bulkiness' counts at the server. Spamassassin and spamd
 use one of these (if dcc checking is enabled) when scoring the
 mail. So is it correct for spamassassin -r to re-submit the mail to
 the DCC servers? My reading of the DCC documentation indicates that it
 should not being so as the mail would have already be counted when
 scanned. 

It is correct: SpamAssassin forces the count all the way up to `spam'
(99) when reporting to DCC. dccproc merely increments the count by
1.

-- 
`One cannot, after all, be expected to read every single word
 of a book whose author one wishes to insult.' --- Richard Dawkins


Re: DCC in Spamassassin

2005-03-14 Thread Norman Zhang
Bill Randle wrote:
I don't have rcddc either. With SpamAssassin, use dccifd as previously
mentioned. Once you edited the dcc_conf file to enable DCCIFD, start it
using the init program:
# /etc/init.d/dccd start
Thanks. dccifd did start. However, I'm seeing the following error message,
dccifd[8337]: clock changed an impossible -1.080998 seconds
May I ask if this is critical?
Regards,
Norman Zhang


Re: DCC in Spamassassin

2005-03-13 Thread Norman Zhang
I also uncommented the DCCIFD_ARGS line.
# used to start dccifd
#   a common value is
#   DCCIFD_ARGS=-SHELO -Smail_host -SSender -SList-ID
DCCIFD_ARGS=
My DCCIFD_ARGS is empty. Should I add the options that is shown above?
Was there a dccd file created in /etc/init.d as part of the
installation process for dcc? It starts dccd, grey, and dccifd. Here's
# ls -l /etc/rc.d/init.d/
-rwx--  1 root root  1406 Mar  1 18:44 amavisd*
-rwx--  1 root root  1101 Jan 28 08:26 clamd*
-rwx--  1 root root  3266 Sep 28 03:32 dccd*
-rwx--  1 root root  1219 Jan 28 08:26 freshclam*
Someone pointed out to me I should look for rcdcc, but I only have
# slocate cdcc
/usr/bin/cdcc
Should I use this instead? BTW do I need to set use_dcc = 0 if I want to 
use dccifd?

Regards,
Norman Zhang


Re: DCC in Spamassassin

2005-03-13 Thread Matt Kettler
At 10:07 PM 3/12/2005, Norman Zhang wrote:
Someone pointed out to me I should look for rcdcc, but I only have
# slocate cdcc
/usr/bin/cdcc
I'm not too familiar with the scripts that come with DCC for this.. I just 
wrote my own init script to start dccifd.


Should I use this instead? BTW do I need to set use_dcc = 0 if I want to 
use dccifd?
No..  SA will use neither dccproc nor dccifd if you do that. The use_dcc 
option completely enables or completely disables all of DCC at once.




RE: DCC in Spamassassin

2005-03-13 Thread Greg Allen
My dcc on RedHat 8.0 is located in

/var/dcc  directory

You should see DCCIFD there as well.

I had to change a line in the /var/dcc/dcc_conf to

DCCIFD_ENABLE=ON

Also, make sure you install the latest DCC with DCCIFD from the Rayolite
website (if you do not have it).

Put the path to DCC in your local spamassassin config file just to be safe.
(local.cf)

DCC_HOME /VAR/DCC

Do all of this and spamassassin should automatically use DCCIFD instead of
DCC when it detects it.







-Original Message-
From: Norman Zhang [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 12, 2005 10:07 PM
To: users@spamassassin.apache.org
Subject: Re: DCC in Spamassassin


 I also uncommented the DCCIFD_ARGS line.

# used to start dccifd
#   a common value is
#   DCCIFD_ARGS=-SHELO -Smail_host -SSender -SList-ID
DCCIFD_ARGS=

My DCCIFD_ARGS is empty. Should I add the options that is shown above?

 Was there a dccd file created in /etc/init.d as part of the
 installation process for dcc? It starts dccd, grey, and dccifd. Here's

# ls -l /etc/rc.d/init.d/
-rwx--  1 root root  1406 Mar  1 18:44 amavisd*
-rwx--  1 root root  1101 Jan 28 08:26 clamd*
-rwx--  1 root root  3266 Sep 28 03:32 dccd*
-rwx--  1 root root  1219 Jan 28 08:26 freshclam*

Someone pointed out to me I should look for rcdcc, but I only have

# slocate cdcc
/usr/bin/cdcc

Should I use this instead? BTW do I need to set use_dcc = 0 if I want to
use dccifd?

Regards,
Norman Zhang



Re: DCC in Spamassassin

2005-03-13 Thread Bill Randle
On Sat, 2005-03-12 at 19:07 -0800, Norman Zhang wrote:
  I also uncommented the DCCIFD_ARGS line.
 
 # used to start dccifd
 #   a common value is
 #   DCCIFD_ARGS=-SHELO -Smail_host -SSender -SList-ID
 DCCIFD_ARGS=
 
 My DCCIFD_ARGS is empty. Should I add the options that is shown above?

I would.

  Was there a dccd file created in /etc/init.d as part of the
  installation process for dcc? It starts dccd, grey, and dccifd. Here's
 
 # ls -l /etc/rc.d/init.d/
 -rwx--  1 root root  1406 Mar  1 18:44 amavisd*
 -rwx--  1 root root  1101 Jan 28 08:26 clamd*
 -rwx--  1 root root  3266 Sep 28 03:32 dccd*
 -rwx--  1 root root  1219 Jan 28 08:26 freshclam*
 
 Someone pointed out to me I should look for rcdcc, but I only have
 
 # slocate cdcc
 /usr/bin/cdcc
 
 Should I use this instead? BTW do I need to set use_dcc = 0 if I want to 
 use dccifd?

I don't have rcddc either. With SpamAssassin, use dccifd as previously
mentioned. Once you edited the dcc_conf file to enable DCCIFD, start it
using the init program:
# /etc/init.d/dccd start

I see you also have amavisd installed. If you run spamassassin from
amavisd you will need to reload it as well:
# amavisd reload

This will force it to re-read the spamassassin config files and pick up
your use_dcc change (should be set to 1) and look for the dccifd socket.

-Bill




Re: DCC in Spamassassin

2005-03-12 Thread Matt Kettler
At 12:10 AM 3/12/2005, Norman Zhang wrote:
Are the following options set correctly?
dcc_home /usr/sbin
dcc_dccifd_path /usr/sbin/dccifd
dcc_path /usr/sbin
No..
dcc_home should be set to where your dcc config files are
dcc_dccifd_path should not be the path to the dccifd binary, it should be 
the path to the dccifd SOCKET that dccifd creates when it is running. (For 
SA to use dccifd instead of dccproc you must start dccifd and get it 
running as a daemon)

Really, you probably don't need to manually set any of these. SA's defaults 
should work fine, the only thing you might need to set is the path to the 
dccifd socket, depending on how you start dccifd. 



Re: DCC in Spamassassin

2005-03-12 Thread Norman Zhang
Matt Kettler wrote:
At 12:10 AM 3/12/2005, Norman Zhang wrote:
Are the following options set correctly?
dcc_home /usr/sbin
dcc_dccifd_path /usr/sbin/dccifd
dcc_path /usr/sbin
No..
dcc_home should be set to where your dcc config files are
Okay. dcc_home /var/lib/dcc
# ls -l /var/lib/dcc
total 60
-rw-r--r--  1 dcc  dcc   3897 Sep 28 03:32 dcc_conf
srw-rw-rw-  1 root root 0 Mar 11 17:51 dccifd=
-rw-r--r--  1 dcc  dcc825 Sep 28 03:32 flod
-rw-r--r--  1 dcc  dcc561 Sep 28 03:32 grey_flod
-rw-r--r--  1 dcc  dcc500 Sep 28 03:32 grey_whitelist
-rw---  1 dcc  dcc   2556 Sep 28 03:32 ids
drwxr-xr-x  2 dcc  dcc  6 Sep 28 03:32 log/
-rw---  1 dcc  dcc   4460 Sep 28 03:32 map
-rw---  1 dcc  dcc   4460 Sep 28 03:32 map.rpmsave
-rw---  1 dcc  dcc842 Sep 28 03:32 map.txt
drwxr-xr-x  6 dcc  dcc 57 Mar 11 14:38 userdirs/
-rw-r--r--  1 dcc  dcc   3104 Sep 28 03:32 whiteclnt
-rw-r--r--  1 dcc  dcc  12124 Sep 28 03:32 whitecommon
-rw-r--r--  1 dcc  dcc486 Sep 28 03:32 whitelist
dcc_dccifd_path should not be the path to the dccifd binary, it should 
be the path to the dccifd SOCKET that dccifd creates when it is running. 
(For SA to use dccifd instead of dccproc you must start dccifd and get 
it running as a daemon)
I think dccifd socket is created in /var/lib/dcc. Do I specify its 
location in /var/lib/dcc/dcc_conf or dccifd? dccifd seems to be empty.

Really, you probably don't need to manually set any of these. SA's 
defaults should work fine, the only thing you might need to set is the 
path to the dccifd socket, depending on how you start dccifd.
I started dccifd by running
# /usr/sbin/dccifd
manually. Should I set dcc_dccifd_path /var/lib/dcc? Is dcc_path 
/usr/sbin fine?

Regards,
Norman Zhang


Re: DCC in Spamassassin

2005-03-12 Thread Norman Zhang
Norman Zhang wrote:
I think dccifd socket is created in /var/lib/dcc. Do I specify its 
location in /var/lib/dcc/dcc_conf or dccifd? dccifd seems to be empty.
Setting
dcc_dccifd_path /var/lib/dcc/dccifd
solves DCC not found.
Really, you probably don't need to manually set any of these. SA's 
defaults should work fine, the only thing you might need to set is the 
path to the dccifd socket, depending on how you start dccifd.
I started dccifd by running
# /usr/sbin/dccifd
manually. Should I set dcc_dccifd_path /var/lib/dcc? Is dcc_path 
/usr/sbin fine?
# more dcc_conf
...
DCCIFD_ENABLE=off
# used to start dccifd
#   a common value is
#   DCCIFD_ARGS=-SHELO -Smail_host -SSender -SList-ID
DCCIFD_ARGS=
...
Does that need to be changed?
Regards,
Norman Zhang