snowcrash+spamassassin wrote:
>> > but, what ARE the other rules' priorities?
>> >
>> > is there documentation of that? nothing on the wiki that i've found.
>> >
>> Priorities don't exist in released versions SA, only the 3.2 development
>> branch.
>
> as i understand it, fuzzyocr -- which runs with v3.1.x ("SpamAssassin
> 3.1.4 or higher")-- specifically relies on priority to ensure that it
> runs 'last'.
>
> do i understand you correctly that it, then, has no effect with
> v3.1.x? (seems to be working on my system ...)
It should have no affect on any 3.1.x release. That's a 3.2 feature,
added by bug 3109http://issues.apache.org/SpamAssassin/show_bug.cgi?id=3109 > >> As for what's in the devel branch, well, that changes regularly. If >> you're using development snapshots, you should be comfortable reading >> the source code, so that's where you should head. > > i'm not using the dev branch/head. > > i'm using a svn co of the 31 branch, which i understand is the 317 > release, plus bug fixes etc. Maybe.. it could be that the branch you grabbed had the patch. I'm not familiar with direct SVN checkouts. A quick way to check would be to look for the Mail::SpamAssassin::Plugin::Shortcircuit plugin. (should be <perlibspath>/Mail/SpamAssassin/Plugin/Shortcircuit.pm) That said, from looking at the docs for the branch that has the feature, the default priority is 0, and lower numbers go first (ie: most negative first.) > > thanks. >
