Hi,
meta rules starts at the lower priority of the rules they are composed by (diff 
for regression test attached).

If you are using a meta rule that mixes network and non network tests the meta 
rule's priority will be -100.
After some tests, it seems that if you mix DMARC rules (priority 500) with 
other rules, DMARC checks may start earlier then expected.
Is this just not well documented (at least in Mail::SpamAssassin::Conf) ?

 Regards
  Giovanni
Index: t/priorities.t
===================================================================
--- t/priorities.t	(revision 1901238)
+++ t/priorities.t	(working copy)
@@ -3,7 +3,7 @@
 use lib '.'; use lib 't';
 use SATest; sa_t_init("priorities");
 use strict;
-use Test::More tests => 10;
+use Test::More tests => 11;
 
 use Mail::SpamAssassin;
 
@@ -125,6 +125,11 @@
   priority FOO5 -23
   priority FOO1 -28
 
+  meta F006 (1)
+  priority F006 500
+
+  meta F007 (F001 && F006)
+
 });
 
 my $sa = create_saobj({
@@ -151,6 +156,8 @@
 ok assert_rule_pri 'FOO5', -28;
 ok assert_rule_pri 'FOO1', -28;
 
+ok assert_rule_pri 'F007', -28;
+
 # ---------------------------------------------------------------------------
 
 sub assert_rule_pri {

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to