Milter-greylist

manu@... wrote:
> I generally agree that unperfect solutions are better than nothing, but
> this solution has an impact on the config file. If we want to later
> choose a better direction, we'll have to break backward compatibility on
> the config file. That's something I really hate when being in the shoes
> of an administrator, so I try to avoid doing it when I'm in the shoes of
> a developper.

FWIW I have automated script building the config file (there's no other 
way to manage 10,000+ users each with their own greylist settings) so I 
don't think this will be too big of a problem for anyone. If 
greylist.confg format changes later, it's only a few seconds change to 
the script to support different format.

I assume anyone using per-recipient patch would be large ISP like us 
anyway, it doesn't really apply to small systems. (Nobody else had asked 
for it yet, so I'm assuming noone else on this list uses it at an ISP)

You can put warning in the documentation that the syntax is likely to 
change in the future. But this is probably true for most of the 
greylist.conf anyway, not just per-recipient settings.

-Dan