KB> No, you are not. Please note that these are version numbers, not floats. KB> With respect to minor versions, 24 is massively larger than 2...
It's all a usability (http://www.useit.com/alertbox/) problem. You might say SpamAssassin is usability exempt, as it is only for computer pros. But I'm here to give valuable insights of how SpamAssassin looks to we lesser programmers. Just want to let you know. Can't help. Gotta go. Anyway, assuming the user guesses correctly the special world of SpamAssassin version numbers, the UPGRADE file still doesn't mention anything beyond 3.2.0. KB> Anyway, the UPGRADE file and its information is targeted at upgrading KB> minor (or even major versions). Read, when upgrading from 3.1.x (or KB> older) to 3.2.x for example. It mentions incompatibilities or general KB> issues that may need attention when doing such an upgrade. KB> Generally, no such issues exist when upgrading micro versions. Which you KB> in fact did. So it should mention all that. Or better yet see how MediaWiki packages their upgrade instructions. KB> However, you likely just overwrote your changes to local.cf Naw, else it wouldn't say $ head ~/etc/mail/spamassassin/local.cf # This is the right place to customize your installation of SpamAssassin. KD> This is why I don't often install from source. I would but Dreamhost's Debian is too "stable" for me to run my brilliant http://jidanni.org/comp/spam/spamdealer.html "filter on the server" solution whilst enjoying the latest SpamAssassin.
