You should be able to just load it up in a current version of SA and see if it throws any errors.
There's nothing that pops out at me as more problematic for the current version than an old version, but.... On 10/15, Harry Putnam wrote: > trusted_networks 192.168.0. I don't think that was ever necessary, I think 192.168.0.* is included in SA's default guesses if you don't specify a trusted_networks. But I guess that's not documented, and I don't feel like checking the code for it at the moment. Not a problem anyway. > skip_rbl_checks 1 > dns_available no Disabling network checks causes spamassassin to be wrong 5 times as often. 5.35 times as often on non-spam, and 4.25 as often on spam. And I believe that's only if you're running spamassassin with the -L or --local flags. By disabling DNS tests, you disable a significant portion of the network tests, without causing spamassassin to use the different score sets which are optimized for having no network tests. So you're likely to get worse than 5 times as many emails wrong. Maybe you really do need network tests disabled. Weird things happen. But don't disable them lightly. There's more info here: http://wiki.apache.org/spamassassin/UsingNetworkTests The estimate that enabling network tests "halves the false negative rate" is old and I should change it. I guess that means SA has become more dependent on network tests. Kind of sad, but not surprising. -- "Blades don't need reloading." - The Zombie Survival Guide by Max Brooks http://www.ChaosReigns.com
