You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by "Johnny B." <jo...@peakpeak.com> on 2004/05/15 17:50:51 UTC
sa 2.63 / DCCifd / spamd / Problem
hi all,
help. i have dccifd, and dccd running and configured correctly on the same machine i am running spamd. my goal is to use them with spamassassin's duo of spamc/spamd. however it doesnt appear that spamd is checking the mail message with dcc while the command line utility "spamassassin" does. this is evidenced by the X-Spam-DCC header being added with no contents of the DCC check after processing with spamc while contents of the check are added after processing with the "spamassassin" command line utility. in addition the dcc command 'cdcc info' shows how many clients have requested a check against the dcc server and only increments when after using "spamassassin" and not with spamc. i have included below what i have in my spamassassin/local.cf file and have tried running spamd with the debug flag but have been at a loss as to why spamd wont seem to use dcc. any help is appreciated.
skip_rbl_checks 1
required_hits 11
use_terse_report 1
clear_terse_report_template
terse_report Results:
terse_report _HITS_ points, _REQD_ required;
terse_report _SUMMARY_
rewrite_subject 1
subject_tag "(spam rating _HITS_/_REQD_)"
auto_learn 0
user_scores_dsn
DBI:mysql:spamassassin:somehost.somewhere:3306
user_scores_sql_username user
user_scores_sql_password password
user_scores_sql_table userpref
use_dcc 1
dcc_add_header 1
dcc_home /var/dcc
dcc_dccifd_path /var/dcc
Re: sa 2.63 / DCCifd / spamd / Problem
Posted by Alex S Moore <as...@edge.net>.
On Sat, 2004-05-15 at 12:14, Johnny B. wrote:
> hi alex,
>
> i set the path to the absolute path of the socket and it still doenst
> seems to see it. now i did install of dcc after i installed spam
> assassin would this affect it? do you think running perl Makefile.PL
> again would be benificial?
No, that should be no problem. Does running spamassassin with the -D
option tell you anything? Maybe a permissions problem? This should use
the socket and not dccproc.
> and to answer your question on dcc i have in house dcc servers i plan
> to use.
Good answer :>
Alex
Re: sa 2.63 / DCCifd / spamd / Problem
Posted by Alex S Moore <as...@edge.net>.
On Sat, 2004-05-15 at 10:50, Johnny B. wrote:
> help. i have dccifd, and dccd running and configured correctly on the same machine i am running spamd. my goal is to use them with spamassassin's duo of spamc/spamd. however it doesnt appear that spamd is checking the mail message with dcc while the command line utility "spamassassin" does. this is evidenced by the X-Spam-DCC header being added with no contents of the DCC check after processing with spamc while contents of the check are added after processing with the "spamassassin" command line utility. in addition the dcc command 'cdcc info' shows how many clients have requested a check against the dcc server and only increments when after using "spamassassin" and not with spamc. i have included below what i have in my spamassassin/local.cf file and have tried running spamd with the debug flag but have been at a loss as to why spamd wont seem to use dcc. any help is appreciated.
>
> dcc_dccifd_path /var/dcc
>
dcc_dccifd_path needs the full pathname to the dccifd socket. Find
this. In your case, it may be /var/dcc/dccifd.
I also use dcc_path, but I am not sure if it is really required. In
your case, it would point to /var/dcc
Are you using the public dcc servers?
Alex
Re: sa 2.63 / DCCifd / spamd / Problem
Posted by jdow <jd...@earthlink.net>.
From: "Johnny B." <jo...@peakpeak.com>
> hi all,
>
> help. i have dccifd, and dccd running and configured correctly on the same
machine i am running spamd. my goal is to use them with spamassassin's duo
of spamc/spamd. however it doesnt appear that spamd is checking the mail
message with dcc while the command line utility "spamassassin" does. this is
evidenced
Try this in local.cf:
# Allow user rules with spamd even though it is theoretically dangerous
allow_user_rules 1
{^_^}