-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
[This question may be more appropriate for the dev-list, please move as
required]
Hi list,
When I originally wrote the experimental ASN plugin (since then
SpamAssassin-ized and improved by the dev team), my impression was that
headers added by an add_header directive in a *.cf file would be taken
up by Bayes - specifically to allow Bayes to learn "bad networks"
automagically from a "X-Spam-ASN" header.
However, that header seems not to be used by Bayes. The relevant
configuration:
- --- cut ---
add_header all Spammy _SPAMMYTOKENS(5,compact)_
add_header all Hammy _HAMMYTOKENS(5,compact)_
ifplugin Mail::SpamAssassin::Plugin::ASN
asn_lookup asn.routeviews.org _ASN_ _ASNCIDR_
add_header all ASN _ASN_ _ASNCIDR_
endif
- --- cut ---
For mails from this list, I get the following headers (example from a
recent message):
- --- cut ---
X-Spam-ASN: AS3701 140.211.0.0/16
X-Spam-Hammy: 0.000-+--H*Ad:D*spamassassin.apache.org,
0.000-+--Hlist-unsubscribe:sk:users-u,
0.000-+--Hlist-help:sk:users-h,
0.000-+--H*Ad:U*users, 0.000-+--HTo:U*users
X-Spam-Spammy: 0.999-1--belief, 0.913-+--H*r:unknown,
0.900-+--H*x:Outlook,
0.900-+--H*UA:Outlook, 0.890-+--H*UA:Microsoft
- --- cut ---
Almost all messages to this very list get "autolearn=ham", and it's
obvious from the -Hammy header above that SA did consider headers added
at an earlier stage.
What would need to be done/changed/configured to allow learning on the
X-Spam-ASN header?
- -- Matthias
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFG8Wp7xbHw2nyi/okRAkhyAJ9bhLOnZoIozlTWHbXZVniBtJAY7QCgyo6V
F/FlBRqAlvGttuJ/GjwLsLQ=
=lJ2A
-----END PGP SIGNATURE-----
