mail::spamassassin::plugin::replacetags(3pm) [debian man page]

Mail::SpamAssassin::Plugin::ReplaceTags(3pm)		User Contributed Perl Documentation	      Mail::SpamAssassin::Plugin::ReplaceTags(3pm)

NAME

       Mail::SpamAssassin::Plugin::ReplaceTags - tags for SpamAssassin rules

       The plugin allows rules to contain regular expression tags to be used in regular expression rules.  The tags make it much easier to
       maintain complicated rules.

       Warning: This plugin relies on data structures specific to this version of SpamAssasin; it is not guaranteed to work with other versions of
       SpamAssassin.

SYNOPSIS

	 loadplugin    Mail::SpamAssassin::Plugin::ReplaceTags

	 replace_start <
	 replace_end   >

	 replace_tag   A       [a@]
	 replace_tag   G       [gk]
	 replace_tag   I       [il|!1y?xccxcdxcexcfxecxedxeexef]
	 replace_tag   R       [r3]
	 replace_tag   V       (?:[vu]|\/)
	 replace_tag   SP      [s~_-]

	 body	       VIAGRA_OBFU     /(?!viagra)<V>+<SP>*<I>+<SP>*<A>+<SP>*<G>+<SP>*<R>+<SP>*<A>+/i
	 describe      VIAGRA_OBFU     Attempt to obfuscate "viagra"

	 replace_rules VIAGRA_OBFU

RULE DEFINITIONS AND PRIVILEGED SETTINGS

       replace_tag tagname expression
	   Assign a valid regular expression to tagname.

	   Note: It is not recommended to put quantifiers inside the tag, it's better to put them inside the rule itself for greater flexibility.

       replace_pre tagname expression
	   Assign a valid regular expression to tagname.  The expression will be placed before each tag that is replaced.

       replace_inter tagname expression
	   Assign a valid regular expression to tagname.  The expression will be placed between each two immediately adjacent tags that are
	   replaced.

       replace_post tagname expression
	   Assign a valid regular expression to tagname.  The expression will be placed after each tag that is replaced.

       replace_rules list_of_tests
	   Specify a list of symbolic test names (separated by whitespace) of tests which should be modified using replacement tags.  Only simple
	   regular expression body, header, uri, full, rawbody tests are supported.

       replace_start string
       replace_end string
	   String(s) which indicate the start and end of a tag inside a rule.  Only tags enclosed by the start and end strings are found and
	   replaced.

perl v5.14.2							    2011-06-06			      Mail::SpamAssassin::Plugin::ReplaceTags(3pm)

Mail::SpamAssassin::Plugin::ASN(3)			User Contributed Perl Documentation			Mail::SpamAssassin::Plugin::ASN(3)

NAME

       Mail::SpamAssassin::Plugin::ASN - SpamAssassin plugin to look up the Autonomous System Number (ASN) of the connecting IP address.

SYNOPSIS

	loadplugin Mail::SpamAssassin::Plugin::ASN

	asn_lookup asn.routeviews.org _ASN_ _ASNCIDR_

	add_header all ASN _ASN_ _ASNCIDR_

DESCRIPTION

       This plugin uses DNS lookups to the services of "http://www.routeviews.org/" to do the actual work. Please make sure that your use of the
       plugin does not overload their infrastructure - this generally means that you should not use this plugin in a high-volume environment or
       that you should use a local mirror of the zone (see "ftp://ftp.routeviews.org/dnszones/").

TEMPLATE TAGS

       This plugin allows you to create template tags containing the connecting IP's AS number and route info for that AS number.

       The default config will add a header that looks like this:

	X-Spam-ASN: AS24940 213.239.192.0/18

       where "AS24940" is the ASN and "213.239.192.0/18" is the route announced by that ASN where the connecting IP address came from. If the AS
       announces multiple networks (more/less specific), they will all be added to the "_ASNCIDR_" tag, separated by spaces, eg:

	X-Spam-ASN: AS1680 89.138.0.0/15 89.139.0.0/16

CONFIGURATION

       The standard ruleset contains a configuration that will add a header containing ASN data to scanned messages.  The bayes tokenizer will use
       the added header for bayes calculations, and thus affect which BAYES_* rule will trigger for a particular message.

       Note that in most cases you should not score on the ASN data directly.  Bayes learning will probably trigger on the _ASNCIDR_ tag, but
       probably not very well on the _ASN_ tag alone.

SEE ALSO

       http://www.routeviews.org/ - all data regarding routing, ASNs etc

       http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4770 - SpamAssassin Issue #4770 concerning this plugin

STATUS

       No in-depth analysis of the usefulness of bayes tokenization of ASN data has been performed.

ADMINISTRATOR SETTINGS

       asn_lookup asn-zone.example.com [ _ASNTAG_ _ASNCIDRTAG_ ]
	   Use this to lookup the ASN info in the specified zone for the first external IP address and add the AS number to the first specified
	   tag and routing info to the second specified tag.

	   If no tags are specified the AS number will be added to the _ASN_ tag and the routing info will be added to the _ASNCIDR_ tag.  You
	   must specify either none or both of the tags.  Tags must start and end with an underscore.

	   If two or more asn_lookups use the same set of template tags, the results of their lookups will be appended to each other in the
	   template tag values in no particular order.	Duplicate results will be omitted when combining results.  In a similar fashion, you can
	   also use the same template tag for both the AS number tag and the routing info tag.

	   Examples:

	     asn_lookup asn.routeviews.org

	     asn_lookup asn.routeviews.org _ASN_ _ASNCIDR_
	     asn_lookup myview.example.com _MYASN_ _MYASNCIDR_

	     asn_lookup asn.routeviews.org _COMBINEDASN_ _COMBINEDASNCIDR_
	     asn_lookup myview.example.com _COMBINEDASN_ _COMBINEDASNCIDR_

	     asn_lookup in1tag.example.net _ASNDATA_ _ASNDATA_

perl v5.12.1							    2010-03-16					Mail::SpamAssassin::Plugin::ASN(3)