Milter-greylist

> :-)
> Maybe it is not needed anyway - lazyaw is "sexy" enough as it is now.
> And if I needed something too much, I might try to implement it on my
> own - just a pity the sources are not well commented.
> Ondrej

Yes, it is "sexy" but I would like to have even more "sexy".
The lazyaw option is way too global and not generic enough semantically.
My users like to have more flexibility.
I would like to have a dynamic clause for that for example:

racl greylist awoption-match sender,domain rcpt <rcpt0@my.domain>
racl greylist awoption-match domain        rcpt <rcpt1@my.domain>
racl greylist awoption-match sender        rcpt <rcpt2@my.domain>
racl greylist awoption-match none          rcpt <rcpt3@my.domain>

The first line gives for rcpt0 like no lazyaw on for him.
The last line gives for rcpt3 like lazyaw is off for him.
The lines in the middle may give options not possible to do today's version.
(May be the use of one of them is suggested earlier in this thread?)
With this change the existing lazyaw option would give the default behaviour
if no awoption-match clause is defined on an racl line.
This would maintain the backward compatibility of the old config file.
I am not proposing the exact syntax, rather the concept.

Bests,
Attila