1Mail::SpamAssassin::PluUgsienr::CAoSnNt(r3i)buted Perl DMoaciulm:e:nStpaatmiAosnsassin::Plugin::ASN(3)
2
3
4

NAME

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

SYNOPSIS

10        loadplugin Mail::SpamAssassin::Plugin::ASN
11
12        asn_lookup asn.routeviews.org _ASN_ _ASNCIDR_
13
14        add_header all ASN _ASN_ _ASNCIDR_
15

DESCRIPTION

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

TEMPLATE TAGS

25       This plugin allows you to create template tags containing the connect‐
26       ing IP's AS number and route info for that AS number.
27
28       The default config will add a header that looks like this:
29
30        X-Spam-ASN: AS24940 213.239.192.0/18
31
32       where "AS24940" is the ASN and "213.239.192.0/18" is the route
33       announced by that ASN where the connecting IP address came from. If the
34       AS announces multiple networks (more/less specific), they will all be
35       added to the "_ASNCIDR_" tag, separated by spaces, eg:
36
37        X-Spam-ASN: AS1680 89.138.0.0/15 89.139.0.0/16
38

CONFIGURATION

40       The standard ruleset contains a configuration that will add a header
41       containing ASN data to scanned messages.  The bayes tokenizer will use
42       the added header for bayes calculations, and thus affect which BAYES_*
43       rule will trigger for a particular message.
44
45       Note that in most cases you should not score on the ASN data directly.
46       Bayes learning will probably trigger on the _ASNCIDR_ tag, but probably
47       not very well on the _ASN_ tag alone.
48

SEE ALSO

50       http://www.routeviews.org/ - all data regarding routing, ASNs etc
51
52       http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4770 - SpamAssas‐
53       sin Issue #4770 concerning this plugin
54

STATUS

56       Experimental - Dec. 18, 2006
57
58       No in-depth analysis of the usefulness of bayes tokenization of ASN
59       data has been performed.
60

ADMINISTRATOR SETTINGS

62       asn_lookup asn-zone.example.com [ _ASNTAG_ _ASNCIDRTAG_ ]
63           Use this to lookup the ASN info for first external IP address in
64           the specified zone and add the AS number to the first specified tag
65           and routing info to the second specified tag.
66
67           If no tags are specified the AS number will be added to the _ASN_
68           tag and the routing info will be added to the _ASNCIDR_ tag.  You
69           must specify either none or both of the tags.  Tags must start and
70           end with an underscore.
71
72           If two or more asn_lookups use the same set of template tags, the
73           results of their lookups will be appended to each other in the tem‐
74           plate tag values in no particular order.  Duplicate results will be
75           omitted when combining results.  In a similar fashion, you can also
76           use the same template tag for both the AS number tag and the rout‐
77           ing info tag.
78
79           Examples:
80
81             asn_lookup asn.routeviews.org
82
83             asn_lookup asn.routeviews.org _ASN_ _ASNCIDR_
84             asn_lookup myview.example.com _MYASN_ _MYASNCIDR_
85
86             asn_lookup asn.routeviews.org _COMBINEDASN_ _COMBINEDASNCIDR_
87             asn_lookup myview.example.com _COMBINEDASN_ _COMBINEDASNCIDR_
88
89             asn_lookup in1tag.example.net _ASNDATA_ _ASNDATA_
90
91
92
93perl v5.8.8                       2008-01-05Mail::SpamAssassin::Plugin::ASN(3)
Impressum