I get this warning:
plugin: failed to create instance of plugin
Mail::SpamAssassin::Plugin::RelayChecker: Can't locate object method
"new" via package "Mail::SpamAssassin::Plugin::RelayChecker" at (eval
26) line 1.
(This is my own build of SA 3.1.7 on Max OS X Server 10.4 ppc)
It seems to work OK though:
* 3.0 RELAY_CHECKER RELAY: badrdns
(I lowered the score)
Patrick Sneyers
Belgium
Op 3-nov-06, om 03:25 heeft John Rudd het volgende geschreven:
I've put up a new version of Relay checker, in
http://people.ucsc.edu/~jrudd/spamassassin
as as before: put RelayChecker.* wherever you put your plugins.
Changes:
1) The score is now fixed instead of variable. default=6
2) Each test can be ignored (it says skipped, but the test is still
run, it just wont trigger a hit if the option is set to non-zero)
3) I added a "clienthostname" check which looks for static, pool,
client, user, fixed in the hostname. Defaults to being skipped.
4) You can set regular expressions for which untrusted relays to skip
5) You can set regular expressions to automatically pass the
message (don't trigger the rule) if you come to an untrusted relay
that matches
6) You can allow it to pass a message if the auth= field is non-empty
# relaychecker_score 6
# relaychecker_skip_nordns 0
# relaychecker_skip_badrdns 0
# relaychecker_skip_baddns 0
# relaychecker_skip_ipinhostname 0
# relaychecker_skip_dynhostname 0
# relaychecker_skip_clienthostname 1
# relaychecker_skip_ip (regular expression)
# relaychecker_pass_ip (regular expression)
# relaychecker_pass_auth 0
I used some of the code from Billy Huddleston's patch, but
obviously went in a different fundamental direction.
I expect I might, at some point, switch from using a dynamic score
in the plugin, to a normal score. But that's the only change I
expect to make, aside from bug fixes (if there are any), and/or a
switch to using Net::DNS. Oh, and putting it into a tar file and
probably making the usual copyright declaration stuff (since I work
for the UC Regents, it's going to be a berkeley type declaration of
ownership, and GPL for license).
Again, feedback, problem reports, success or horror stories welcome.
JohnR
