# This is the right place to customize your installation of SpamAssassin. # See 'perldoc Mail::SpamAssassin::Conf' for details of what can be # tweaked. # ########################################################################### # rewrite_subject 1 #report_safe 1 header SUBJ_RETHANKS Subject =~ /Re\: Thanks \:\)/ describe SUBJ_RETHANKS Subject is "Re: Thanks :)" score SUBJ_RETHANKS 10 10 10 10
now its correct ? -----Messaggio originale----- Da: Paolo Cravero as2594 [mailto:[EMAIL PROTECTED] Inviato: mercoledì 18 maggio 2005 11.42 A: users@spamassassin.apache.org Oggetto: Re: R: German Spam Netmail wrote: > Ok > Now this is my config file > # This is the right place to customize your installation of SpamAssassin. > # See 'perldoc Mail::SpamAssassin::Conf' for details of what can be > # tweaked. > # > ########################################################################### > # > rewrite_subject 1 > #report_safe 1 > > If i want add block for the header of message ..how to ? Altought custom rules on a particular text is not the best way to achieve SpamAssassin potential, you need to add to local.cf something like: header SUBJ_RETHANKS Subject =~ /Re\: Thanks \:\)/ describe SUBJ_RETHANKS Subject is "Re: Thanks :)" score SUBJ_RETHANKS 10 10 10 10 # Gives 10 points to those messages whose subject is "Re: Thanks :)" You need to be able to write Perl regexps if you want to be more successful. You should test new rules on a development server, not on your primary box. Don't forget to run spamassassin --lint before you put any new rule/ruleset into production! Custom rules are very time consuming for the sysadmin, especially if not well written. There are enough free resources (rulesemporium) to keep SpamAssassin's hit ratio very high. And please do not forget that the Bayesian filter is your Friend! SpamAssassin is _extremely_ well documented. Paolo -- SpamAssassin-based email antispam/antivirus solutions Italian/English-to/from-Croatian translations