Milter-greylist

With milter-greylist 4.2.7 and the configuration below (plus the default SPF racl whitelisting), blocking > 11 is working, but the "spamd > 6" line appears never to be reached. I see some discussion in the archives of whether greylisting based on content is a good idea, but the assumption seemed to be that, technically, it would work.

 dacl whitelist list "my network" nolog
 dacl whitelist msgsize > 400k
 dacl blacklist spamd > 11 msg "Your message is considered spam"
 dacl greylist  spamd > 6 delay 30m autowhite 2d msg "Message delayed due to suspect spam content"
 racl greylist default delay 10m autowhite 14d

What are the precedence rules, if any, governing "racl whitelist" and dacl whitelist/blacklist/greylist? Does racl whitelist or racl greylist expiry ever trump dacl blacklist, for example?

Independent second question:

I'd like milter-greylist to leave an X-Spam header so that a downstream MDA can drop the message into the Junk folder. I'll probably also change from CHECK to SYMBOLS. Does anyone have a patch for this already? If not, I'll submit something. I know I have a choice of spamassassin-specific milters, but the idea of doing everything in one is appealing.
-- 
Rich Graves http://claimid.com/rcgraves

Rich Graves <rgraves@...> wrote:

> What are the precedence rules, if any, governing "racl whitelist" and dacl
> whitelist/blacklist/greylist? Does racl whitelist or racl greylist
> expiry ever trump dacl blacklist, for example?

We stop evaluation on the first matching rule.

> I'd like milter-greylist to leave an X-Spam header so that a downstream
> MDA can drop the message into the Junk folder. I'll probably also change
> from CHECK to SYMBOLS. 

You mean you want milter-greylist to alter a header? I will implement
that if nobody do it, I alsoneed the feature. But do not hold your
breath on it.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...