Milter-greylist

Emmanuel Dreyfus <manu@...> writes:

> It would just not whitelist, and the message would go through greylisting.
> Not something really horrible.

Oooops, that make sense. I was into another galaxy when I wrote it, I'm
going to drink another coffee ;^)

> Oh, yes, good idea. In fact, per-user config could be made more general:
> per recipient config, where the recipient can be given as a regex. That
> way you can give a domain if you want.

Yep, it's nice.

> That's something for releases beyond 1.4: too intrusive. But we can 
> still discuss the user interface. What about this?
>
> rcpt /.*example\.com$/ {
> 	lazyaw
> 	report none
> 	autowhite 3d
> }

Why not, I agree with the use of sections in the configuration file. 

> One problem to solve: how to handle multiple matches?

I think that, here, the choice is whether milter-greylist processes first
match of last match. Trying anything else would end into code complexity
and fuzzy behaviour under some circumstances.