You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Phibee Network operation Center <no...@phibee.net> on 2005/05/16 11:36:42 UTC
SpamAssassin 3.0 and test/check a .cf file ?
Hi
i am new into SPamAssassin and i want know if they have a tools for check
a personnal .cf files for see if he don't have a error.
Thanks for your help
Re: SpamAssassin 3.0 and test/check a .cf file ?
Posted by Loren Wilton <lw...@earthlink.net>.
config: SpamAssassin failed to parse line, skipping: rewrite_subject 1
config: SpamAssassin failed to parse line, skipping: report_header 1
config: SpamAssassin failed to parse line, skipping: use_terse_report 1
config: SpamAssassin failed to parse line, skipping: defang_mime 1
config: SpamAssassin failed to parse line, skipping:
auto_report_threshold 30
config: SpamAssassin failed to parse line, skipping: auto_learn 1
warning: description exists for non-existent rule RCVD_IN_OPM_WINGATE
warning: description for RATWARE_EGROUPS is over 50 chars
warning: description for EXCUSE_3 is over 50 chars
warning: description for FULL_REFUND is over 50 chars
warning: description for RCVD_IN_BSP_TRUSTED is over 50 chars
warning: description for FORGED_TELESP_RCVD is over 50 chars
warning: description for FROM_NO_LOWER is over 50 chars
<...> # Why this Warning, it's a default rules of spamassassin 3.0.1
Because these are 2.6x or earlier rules. You probably have rules files in
two different places.
Loren
Re: SpamAssassin 3.0 and test/check a .cf file ?
Posted by Matt Kettler <mk...@evi-inc.com>.
Phibee Network operation Center wrote:
>
> Thanks Christoph for your answer,
>
> i have see a big quantity of error into my .cf file ;=) goods i have
> resolved it ..
>
> In the debug, i have a information that i don't understand :
>
> =====================================================================
> config: SpamAssassin failed to parse line, skipping: timelog_path
> /var/log/spamassassin
> config: SpamAssassin failed to parse line, skipping: rewrite_subject 1
> config: SpamAssassin failed to parse line, skipping: report_header 1
> config: SpamAssassin failed to parse line, skipping: use_terse_report 1
> config: SpamAssassin failed to parse line, skipping: defang_mime 1
> config: SpamAssassin failed to parse line, skipping:
> auto_report_threshold 30
> config: SpamAssassin failed to parse line, skipping: auto_learn 1
>
<snip>
>
> why he failed to parse line ?
Because all of those options are from old versions of SA and are no longer
supported.
I take it you used the web form to generate a config file. That generator is
only good for SA 2.5x at this time.
auto_learn became bayes_auto_learn when 2.60 was released.
defang_mime and report_header both became obsolete when SA 2.60 introduced
"report_safe", which has all the same functionality.
use_terse_report was deprecated when SA 2.60 was released, as a combination of
report_safe and the report templates made it redundant.
timelog_path was removed when 2.60 was released.
rewrite_subject got replaced by rewrite_header in SA 3.0, which allows more
flexibility in tagging, not just subject lines.
Re: SpamAssassin 3.0 and test/check a .cf file ?
Posted by Phibee Network operation Center <no...@phibee.net>.
Thanks Christoph for your answer,
i have see a big quantity of error into my .cf file ;=) goods i have
resolved it ..
In the debug, i have a information that i don't understand :
=====================================================================
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8bd19a8)
inhibited further callbacks
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8bd19a8)
inhibited further callbacks
config: SpamAssassin failed to parse line, skipping: timelog_path
/var/log/spamassassin
config: SpamAssassin failed to parse line, skipping: rewrite_subject 1
config: SpamAssassin failed to parse line, skipping: report_header 1
config: SpamAssassin failed to parse line, skipping: use_terse_report 1
config: SpamAssassin failed to parse line, skipping: defang_mime 1
config: SpamAssassin failed to parse line, skipping:
auto_report_threshold 30
config: SpamAssassin failed to parse line, skipping: auto_learn 1
warning: description exists for non-existent rule RCVD_IN_OPM_WINGATE
warning: description for RATWARE_EGROUPS is over 50 chars
warning: description for EXCUSE_3 is over 50 chars
warning: description for FULL_REFUND is over 50 chars
warning: description for RCVD_IN_BSP_TRUSTED is over 50 chars
warning: description for FORGED_TELESP_RCVD is over 50 chars
warning: description for FROM_NO_LOWER is over 50 chars
<...> # Why this Warning, it's a default rules of spamassassin 3.0.1
debug: using "/root/.spamassassin" for user state dir
debug: bayes: no dbs present, cannot tie DB R/O:
/root/.spamassassin/bayes_toks
debug: Score set 1 chosen.
debug: metadata: X-Spam-Relays-Trusted:
debug: metadata: X-Spam-Relays-Untrusted:
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8bd19a8)
implements 'parsed_metadata'
debug: dns_available set to yes in config file, skipping test
debug: decoding: no encoding detected
debug: URIDNSBL: domains to query:
debug: is Net::DNS::Resolver available? yes
debug: Net::DNS version: 0.48
debug: all '*From' addrs: ignore@compiling.spamassassin.taint.org
debug: Running tests for priority: 0
debug: running header regexp tests; score so far=0
=====================================================================
why he failed to parse line ?
Thanks
Christoph Petersen a écrit :
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Hi,
>
>Phibee Network operation Center schrieb:
>
>
>>Hi
>>
>>i am new into SPamAssassin and i want know if they have a tools for check
>>a personnal .cf files for see if he don't have a error.
>>
>>
>>
>
>Try spamassassin -D --lint. It will check all of your config files.
>
>
>
>>Thanks for your help
>>
>>
>
>Greets
>
>- --
>Christoph Petersen
>
>Öffentlicher Schlüssel:
>http://www.peterschen.de/files/lists@peterschen.de.asc
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.0 (MingW32)
>
>iD8DBQFCiG3EXt+Pa5qk0X4RArAhAKCWo64lyh5ioEXyzK7HoXSQVtn2CgCeOBk2
>CJ2dgbOluu+eOALAMI7BWuI=
>=ddSU
>-----END PGP SIGNATURE-----
>
>
>
>
Re: SpamAssassin 3.0 and test/check a .cf file ?
Posted by Christoph Petersen <li...@peterschen.de>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Phibee Network operation Center schrieb:
> Hi
>
> i am new into SPamAssassin and i want know if they have a tools for check
> a personnal .cf files for see if he don't have a error.
>
Try spamassassin -D --lint. It will check all of your config files.
> Thanks for your help
Greets
- --
Christoph Petersen
Öffentlicher Schlüssel:
http://www.peterschen.de/files/lists@peterschen.de.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
iD8DBQFCiG3EXt+Pa5qk0X4RArAhAKCWo64lyh5ioEXyzK7HoXSQVtn2CgCeOBk2
CJ2dgbOluu+eOALAMI7BWuI=
=ddSU
-----END PGP SIGNATURE-----