problem in updating the spam database with rulesdujour

2006-10-30 Thread ankush grover 

hey friends,

I am using spamassassin 3.1.3 on Fc3 along with postfix +
mailscanner. I have configured rulesdujour to download latest spam
rules. When I tried to ran the rulesdujour script I got the following
errors at the end.


Lint output: [6769] warn: config: failed to parse line, skipping:
AUTOBAN: Over 500 *.cf requests in 48 hours period - Check your CRON
[6769] warn: config: failed to parse line, skipping: CONTACT:
[EMAIL PROTECTED]
[6769] warn: config: failed to parse line, skipping: AUTOBAN: Over 500
*.cf requests in 48 hours period - Check your CRON
[6769] warn: config: failed to parse line, skipping: CONTACT:
[EMAIL PROTECTED]
[6769] warn: config: failed to parse line, skipping: AUTOBAN: Over 500
*.cf requests in 48 hours period - Check your CRON
[6769] warn: config: failed to parse line, skipping: CONTACT:
[EMAIL PROTECTED]
[6769] warn: lint: 66 issues detected, please rerun with debug enabled
for more information

there are many lines with the same error I am omitting those lines to
keep this mail short

**WARNING***: spamassassin --lint failed.
Rolling configuration files back, not restarting SpamAssassin.


I ran spamassassin in debug mode

spamassassin -D --lint


[7957] dbg: config: read file /etc/mail/spamassassin/tripwire.cf
[7957] dbg: config: using /root/.spamassassin for user state dir
[7957] dbg: config: using /root/.spamassassin/user_prefs for user prefs file
[7957] dbg: config: read file /root/.spamassassin/user_prefs
[7957] dbg: plugin: loading Mail::SpamAssassin::Plugin::URIDNSBL from @INC
[7957] dbg: plugin: registered
Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x9c0afb8)
[7957] dbg: plugin: loading Mail::SpamAssassin::Plugin::Hashcash from @INC
[7957] dbg: plugin: registered
Mail::SpamAssassin::Plugin::Hashcash=HASH(0x9c1c2b0)
[7957] dbg: plugin: loading Mail::SpamAssassin::Plugin::SPF from @INC
[7957] dbg: plugin: registered Mail::SpamAssassin::Plugin::SPF=HASH(0x9c4d27c)
[7957] dbg: plugin: loading Mail::SpamAssassin::Plugin::Pyzor from @INC
[7957] dbg: pyzor: network tests on, attempting Pyzor
[7957] dbg: plugin: registered Mail::SpamAssassin::Plugin::Pyzor=HASH(0x9c4ff00)
[7957] dbg: plugin: loading Mail::SpamAssassin::Plugin::SpamCop from @INC
[7957] dbg: reporter: network tests on, attempting SpamCop
[7957] dbg: plugin: registered
Mail::SpamAssassin::Plugin::SpamCop=HASH(0x9c2b8b4)
[7957] dbg: plugin: loading Mail::SpamAssassin::Plugin::AWL from @INC
[7957] dbg: plugin: registered Mail::SpamAssassin::Plugin::AWL=HASH(0x9cd44f0)
[7957] dbg: plugin: loading
Mail::SpamAssassin::Plugin::AutoLearnThreshold from @INC
[7957] dbg: plugin: registered
Mail::SpamAssassin::Plugin::AutoLearnThreshold=HASH(0x9ce1ebc)
[7957] dbg: plugin: loading
Mail::SpamAssassin::Plugin::WhiteListSubject from @INC
[7957] dbg: plugin: registered
Mail::SpamAssassin::Plugin::WhiteListSubject=HASH(0x9ceb774)
[7957] dbg: plugin: loading Mail::SpamAssassin::Plugin::MIMEHeader from @INC
[7957] dbg: plugin: registered
Mail::SpamAssassin::Plugin::MIMEHeader=HASH(0x9cf5924)
[7957] dbg: plugin: loading Mail::SpamAssassin::Plugin::ReplaceTags from @INC
[7957] dbg: plugin: registered
Mail::SpamAssassin::Plugin::ReplaceTags=HASH(0x9cee358)
[7957] dbg: plugin: fixed relative path:
/var/lib/spamassassin/3.001003/saupdates_openprotect_com/70_sare_adult.cf
[7957] dbg: config: using
/var/lib/spamassassin/3.001003/saupdates_openprotect_com/70_sare_adult.cf
for included file
[7957] dbg: config: read file
/var/lib/spamassassin/3.001003/saupdates_openprotect_com/70_sare_adult.cf
[7957] dbg: plugin: fixed relative path:
/var/lib/spamassassin/3.001003/saupdates_openprotect_com/70_sare_bayes_poison_nxm.cf
[7957] dbg: config: using
/var/lib/spamassassin/3.001003/saupdates_openprotect_com/70_sare_bayes_poison_nxm.cf
for included file
[7957] dbg: config: read file
/var/lib/spamassassin/3.001003/saupdates_openprotect_com/70_sare_bayes_poison_nxm.cf
[7957] dbg: plugin: fixed relative path:
/var/lib/spamassassin/3.001003/saupdates_openprotect_com/70_sare_evilnum0.cf
[7957] dbg: config: using
/var/lib/spamassassin/3.001003/saupdates_openprotect_com/70_sare_evilnum0.cf
for included file
[7957] dbg: config: read file
/var/lib/spamassassin/3.001003/saupdates_openprotect_com/70_sare_evilnum0.cf
[7957] dbg: plugin: fixed relative path:
/var/lib/spamassassin/3.001003/saupdates_openprotect_com/70_sare_evilnum1.cf
[7957] dbg: config: using
/var/lib/spamassassin/3.001003/saupdates_openprotect_com/70_sare_evilnum1.cf
for included file
[7957] dbg: config: read file
/var/lib/spamassassin/3.001003/saupdates_openprotect_com/70_sare_evilnum1.cf
[7957] dbg: plugin: fixed relative path:
/var/lib/spamassassin/3.001003/saupdates_openprotect_com/70_sare_genlsubj0.cf
[7957] dbg: config: using
/var/lib/spamassassin/3.001003/saupdates_openprotect_com/70_sare_genlsubj0.cf
for included file
[7957] dbg: config: read file
/var/lib/spamassassin/3.001003/saupdates_openprotect_com/70_sare_genlsubj0.cf
[7957] dbg: plugin: fixed relative path:

Re: problem in updating the spam database with rulesdujour

2006-10-30 Thread Vidar Tyldum Hansen 
ankush grover, 30.10.2006 13:04:
 hey friends,
 
 I am using spamassassin 3.1.3 on Fc3 along with postfix +
 mailscanner. I have configured rulesdujour to download latest spam
 rules. When I tried to ran the rulesdujour script I got the following
 errors at the end.
 
 
 Lint output: [6769] warn: config: failed to parse line, skipping:
 AUTOBAN: Over 500 *.cf requests in 48 hours period - Check your CRON
 [6769] warn: config: failed to parse line, skipping: CONTACT:
 [EMAIL PROTECTED]
 [6769] warn: config: failed to parse line, skipping: AUTOBAN: Over 500
 *.cf requests in 48 hours period - Check your CRON
 [6769] warn: config: failed to parse line, skipping: CONTACT:
 [EMAIL PROTECTED]
 [6769] warn: config: failed to parse line, skipping: AUTOBAN: Over 500
 *.cf requests in 48 hours period - Check your CRON
 [6769] warn: config: failed to parse line, skipping: CONTACT:
 [EMAIL PROTECTED]

Have you checked your cron like the error suggests? Seems you are
flooding the servers. How often is rdj ran? Have you 'tested' a lot?

-- 
Cheers
Vidar Tyldum Hansen

Re: problem in updating the spam database with rulesdujour

2006-10-30 Thread ankush grover 


Have you checked your cron like the error suggests? Seems you are
flooding the servers. How often is rdj ran? Have you 'tested' a lot?

--

hey,

Actullay other admin set the wrong crontab . Yes the script has ran
atleast 5 times a day before I posted this problem I have disable the
script for 1 day. Hopefully things will cool down.

Ankush Grover