Spamassassin - problem s parsingem conf. souboru
Zdarek,
hodil jsem na debian (jadro 2.4.24) spamassassin pro bezici sendmail. Mam ho temer defaultne nastaveny, ale neni fuknci - debug hlasi chybu pri parsingu defaultnich conf. souboru. Pridal jsem i do /etc/spamassassin/init.pre radek LoadPlugin Mail::Spamassassin::Conf::Parser, ale nepomaha to. Tusi nekdo ? Na www spamassassinnu jsem nic ohledne tohoto neobjevil
Kód:
angelaold:/etc/spamassassin# spamassassin --debug --lint
debug: SpamAssassin version 3.0.3
debug: Score set 0 chosen.
debug: running in taint mode? yes
debug: Running in taint mode, removing unsafe env vars, and resetting PATH
debug: PATH included '/usr/local/sbin', keeping.
debug: PATH included '/usr/local/bin', keeping.
debug: PATH included '/usr/sbin', keeping.
debug: PATH included '/usr/bin', keeping.
debug: PATH included '/sbin', keeping.
debug: PATH included '/bin', keeping.
debug: PATH included '/usr/bin/X11', keeping.
debug: Final PATH set to: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11
debug: diag: module installed: DBI, version 1.46
debug: diag: module installed: DB_File, version 1.808
debug: diag: module installed: Digest::SHA1, version 2.10
debug: diag: module installed: IO::Socket::UNIX, version 1.21
debug: diag: module installed: MIME::Base64, version 3.04
debug: diag: module installed: Net::DNS, version 0.48
debug: diag: module installed: Net::LDAP, version 0.33
debug: diag: module installed: Razor2::Client::Agent, version 2.67
debug: diag: module installed: Storable, version 2.15
debug: diag: module installed: URI, version 1.35
debug: ignore: using a test message to lint rules
debug: using "/etc/spamassassin/init.pre" for site rules init.pre
debug: config: read file /etc/spamassassin/init.pre
debug: using "/usr/share/spamassassin" for default rules dir
debug: config: read file /usr/share/spamassassin/10_misc.cf
debug: config: read file /usr/share/spamassassin/20_anti_ratware.cf
debug: config: read file /usr/share/spamassassin/20_body_tests.cf
debug: config: read file /usr/share/spamassassin/20_compensate.cf
debug: config: read file /usr/share/spamassassin/20_dnsbl_tests.cf
debug: config: read file /usr/share/spamassassin/20_drugs.cf
debug: config: read file /usr/share/spamassassin/20_fake_helo_tests.cf
debug: config: read file /usr/share/spamassassin/20_head_tests.cf
debug: config: read file /usr/share/spamassassin/20_html_tests.cf
debug: config: read file /usr/share/spamassassin/20_meta_tests.cf
debug: config: read file /usr/share/spamassassin/20_phrases.cf
debug: config: read file /usr/share/spamassassin/20_porn.cf
debug: config: read file /usr/share/spamassassin/20_ratware.cf
debug: config: read file /usr/share/spamassassin/20_uri_tests.cf
debug: config: read file /usr/share/spamassassin/23_bayes.cf
debug: config: read file /usr/share/spamassassin/25_body_tests_es.cf
debug: config: read file /usr/share/spamassassin/25_hashcash.cf
debug: config: read file /usr/share/spamassassin/25_spf.cf
debug: config: read file /usr/share/spamassassin/25_uribl.cf
debug: config: read file /usr/share/spamassassin/30_text_de.cf
debug: config: read file /usr/share/spamassassin/30_text_fr.cf
debug: config: read file /usr/share/spamassassin/30_text_nl.cf
debug: config: read file /usr/share/spamassassin/30_text_pl.cf
debug: config: read file /usr/share/spamassassin/50_scores.cf
debug: config: read file /usr/share/spamassassin/60_whitelist.cf
debug: config: read file /usr/share/spamassassin/65_debian.cf
debug: using "/etc/spamassassin" for site rules dir
debug: config: read file /etc/spamassassin/10_misc.cf
debug: config: read file /etc/spamassassin/20_head_tests.cf
debug: config: read file /etc/spamassassin/20_uri_tests.cf
debug: config: read file /etc/spamassassin/25_body_tests_es.cf
debug: config: read file /etc/spamassassin/25_body_tests_pl.cf
debug: config: read file /etc/spamassassin/25_head_tests_pl.cf
debug: config: read file /etc/spamassassin/30_text_es.cf
debug: config: read file /etc/spamassassin/30_text_pl.cf
debug: config: read file /etc/spamassassin/40_spam_phrases.cf
debug: config: read file /etc/spamassassin/50_scores.cf
debug: config: read file /etc/spamassassin/60_whitelist.cf
debug: config: read file /etc/spamassassin/65_debian.cf
debug: config: read file /etc/spamassassin/local.cf
debug: using "/root/.spamassassin" for user state dir
debug: using "/root/.spamassassin/user_prefs" for user prefs file
debug: config: read file /root/.spamassassin/user_prefs
debug: plugin: loading Mail::SpamAssassin::Plugin::URIDNSBL from @INC
debug: plugin: registered Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x857f100)
debug: plugin: loading Mail::SpamAssassin::Plugin::Hashcash from @INC
debug: plugin: registered Mail::SpamAssassin::Plugin::Hashcash=HASH(0x91091f8)
debug: plugin: loading Mail::SpamAssassin::Plugin::SPF from @INC
debug: plugin: registered Mail::SpamAssassin::Plugin::SPF=HASH(0x90cfa24)
debug: plugin: loading Mail::SpamAssassin::PerMsgStatus from @INC
debug: plugin: registered Mail::SpamAssassin::PerMsgStatus=HASH(0x90cfb38)
debug: plugin: loading Mail::SpamAssassin::Conf::Parser from @INC
debug: plugin: registered Mail::SpamAssassin::Conf::Parser=HASH(0x90cfbec)
debug: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x857f100) implements 'parse_config'
debug: plugin: Mail::SpamAssassin::Plugin::Hashcash=HASH(0x91091f8) implements 'parse_config'
config: SpamAssassin failed to parse line, skipping: clear-spamtrap-template
config: SpamAssassin failed to parse line, skipping: spamtrap Subject: this address is no longer available
config: SpamAssassin failed to parse line, skipping: spamtrap [this message has been automatically generated]
config: SpamAssassin failed to parse line, skipping: spamtrap
config: SpamAssassin failed to parse line, skipping: spamtrap Please note that this address is no longer in use, and nowadays
config: SpamAssassin failed to parse line, skipping: spamtrap receives nothing but unsolicited commercial mail. Accordingly,
config: SpamAssassin failed to parse line, skipping: spamtrap any mail sent to it is added to several spam-tracking databases,
config: SpamAssassin failed to parse line, skipping: spamtrap then automatically deleted.
config: SpamAssassin failed to parse line, skipping: spamtrap
config: SpamAssassin failed to parse line, skipping: spamtrap If you genuinely want to contact the owner of the address, please
config: SpamAssassin failed to parse line, skipping: spamtrap re-check your contact lists, or search the web, to find their
config: SpamAssassin failed to parse line, skipping: spamtrap current e-mail address.
config: SpamAssassin failed to parse line, skipping: spamtrap
config: SpamAssassin failed to parse line, skipping: spamtrap The mail you sent is reproduced in full below, for resending to
config: SpamAssassin failed to parse line, skipping: spamtrap the correct address. Sorry for the inconvenience!
config: SpamAssassin failed to parse line, skipping: spamtrap
config: SpamAssassin failed to parse line, skipping: spamtrap [-- Signed: the SpamAssassin mail filter]
config: SpamAssassin failed to parse line, skipping: spamtrap
config: SpamAssassin failed to parse line, skipping: clear-terse-report-template
config: SpamAssassin failed to parse line, skipping: terse-report ---- Start SpamAssassin results
config: SpamAssassin failed to parse line, skipping: terse-report _HITS_ hits, _REQD_ required;
config: SpamAssassin failed to parse line, skipping: terse-report _SUMMARY_
config: SpamAssassin failed to parse line, skipping: terse-report ---- End of SpamAssassin results
config: SpamAssassin failed to parse line, skipping: auto_report_threshold 30
zkraceny vypis, nema smysl to posilat cele...
Re: Spamassassin - problem s parsingem conf. souboru
To vypada na nejaky paznaky v tom konfigu. Zkus to prohlildnout v nejakym editoru co ti je zobrazi.
Re: Spamassassin - problem s parsingem conf. souboru
Tohle je 10_misc.cf, ktery jsem menil jen na konci (momentalne to tam je zakomentovane). Zadny problem v tom nevidim. Je zajimave, ze clear-report-template je ok, ale to co je po nem, uz je vadny. Pritom to je default :( Instalovano pres dselect...:???:
Kód:
# SpamAssassin rules file. See 'man Mail::SpamAssassin::Conf' for details.
###########################################################################
# Default template. Try to keep it under 76 columns (inside the the dots below).
# Bear in mind that EVERY line will be prefixed with "SPAM: " in order to make
# it clear what's been added, and allow other filters to *remove* spamfilter
# modifications, so you lose 6 columns right there.
#
# ......................................................................
clear-report-template
report -------------------- Start SpamAssassin results ----------------------
report This mail is probably spam. The original message has been altered
report so you can recognise or block similar unwanted mail in future.
report See http://spamassassin.org/tag/ for more details.
report
report mailto:webmaster@impuls.cz
report
report Content analysis details: (_HITS_ hits, _REQD_ required)
report _SUMMARY_
report -------------------- End of SpamAssassin results ---------------------
# ......................................................................
###########################################################################
# and now, a template for spam-trap responses. If the first few lines
# begin with "Xxxxxx: " where Xxxxxx is a header, they'll be used as
# headers.
clear-spamtrap-template
spamtrap Subject: this address is no longer available
spamtrap [this message has been automatically generated]
spamtrap
spamtrap Please note that this address is no longer in use, and nowadays
spamtrap receives nothing but unsolicited commercial mail. Accordingly,
spamtrap any mail sent to it is added to several spam-tracking databases,
spamtrap then automatically deleted.
spamtrap
spamtrap If you genuinely want to contact the owner of the address, please
spamtrap re-check your contact lists, or search the web, to find their
spamtrap current e-mail address.
spamtrap
spamtrap The mail you sent is reproduced in full below, for resending to
spamtrap the correct address. Sorry for the inconvenience!
spamtrap
spamtrap [-- Signed: the SpamAssassin mail filter]
spamtrap
###########################################################################
# Terse report template.
#
#............................................................................
clear-terse-report-template
terse-report ---- Start SpamAssassin results
terse-report _HITS_ hits, _REQD_ required;
terse-report _SUMMARY_
terse-report ---- End of SpamAssassin results
#............................................................................
###########################################################################
# Database configuration options.
#
# user_scores_dsn MUST be in the form:
# DBI:databasetype:databasename:hostname:port
# ex. DBI:mysql:spamassassin:localhost
#
# user_scores_sql_username is the authorized username to connect to DSN
# user_scores_sql_password is the password for the database username
#user_scores_dsn DBI:mysql:spamassassin:localhost
#user_scores_sql_username spam
#user_scores_sql_password spamfilter
###########################################################################
# Automatic-whitelist directory, for the default db-based whitelist
# backend. By default, each user has their own, in their ~/.spamassassin
# directory with mode 0600, but for system-wide SpamAssassin use, you may
# want to share this across all users; uncomment and customise the below
# lines. (Make sure the mode has --x bits set.)
auto_whitelist_factor 0.5
# default: per-user whitelist:
#auto_whitelist_path ~/.spamassassin/auto-whitelist
#auto_whitelist_file_mode 0600
# use this for a system-wide whitelist:
auto_whitelist_path /var/spool/spamassassin/auto-whitelist
auto_whitelist_file_mode 0666
###########################################################################
# Default prefs values: users can override these in their
# ~/.spamassassin.prefs files.
# How many hits before a mail is considered spam.
required_hits 5
# How many hits before a mail is automatically reported to blacklisting
# services like Razor. Be very careful with this; you really should manually
# verify the spamminess of a mail before reporting it.
auto_report_threshold 30
# Mail using languages used in these country codes will not be marked
# as being possibly spam in a foreign language.
#
ok_locales cz
# Some common prefs settings can be set here, to take effect site-wide
# unless the user override them. See the .prefs file for explanations.
#rewrite_subject 1
#report_header 0
# subject_tag *****SPAM*****
#use_terse_report 0
# defang_mime 1
#skip_rbl_checks 0
#check_mx_attempts 3
#check_mx_delay 5
