https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6508
--- Comment #3 from Mark Martinec <[email protected]> 2010-11-04 19:56:51 UTC --- > In my experience this has been an important feature. > I know of a number of people that have setups like this: > trusted_networks 10.20.30.0/24 > internal_networks 10.20.30.0/24 !10.20.30.2/31 > Where the /24 covers their MXes and the /31 covers their MSAs. The above produces a lint warning: $ spamassassin --lint warn: netset: cannot exclude 10.20.30.2/31 as it has already been included Similarly, of the six failing test cases in trust_path.t all but one produce a lint warning (if I counted correctly). The remaining one is perhaps questionable or maybe a lint test can be added. We have been telling people they cannot expect flawless operation in presence of lint errors or warnings. Following a principle of 'garbage-in, garbage-out', maintaining backwards compatibility with invalid setups is not always necessary or possible, especially when warnings _are_ being issued. But I agree the concept of these three sets of networks is hard to understand and may not even be applicable to every topology, so any hand-guiding in a form of documentation with examples and warnings is more than welcome. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
