Milter-greylist

[Reviving an old discussion...]

--- In milter-greylist@yahoogroups.com, shuttlebox <shuttlebox@...> wrote:
>
> I realize it's probably too late for the next stable and I don't even
> know if it has been discussed before but I would really like to see an
> include option in greylist.conf similar to what BIND DNS has for
> named.conf:
> 
> http://www.zytrax.com/books/dns/ch7/include.html
> 
> Basically, wherever "include <file>" is encountered it's replaced with
> the contents of <file>. Reasons are the same as in the link above.
> 
> I'm ok with a change in one of the included files not triggering a
> reload but that we have to HUP ourselves. That's not a problem.
> 
> What do others think? I love the syntax of greylist.conf and often use
> it instead of Sendmail, if only I had the above feature I could
> integrate log parsing scripts that would blacklist spammers, I don't
> want to mess with the main file for that.
> 
> /peter bonivart
>

This would also make distribution maintaining easier. Parts of the file maintained by the distributor (socket location for example) or parts maintained upstream (the list of broken MTAs) can be updated without affecting the main config, that the user surely edited.

So what exactly is the problem about this feature?

Code bloat? The syntax is already quite interesting. It wouldn't add really much more complexity, IMHO.

That said, one option is of course to use m4 or cpp outside of milter-greylist and let m4/cpp create the final config from some source files. Like what sendmail.mc is doing. Then we can use m4's include() and be done.

As one bug part of the shipped config is the list of broken MTAs, it would be good if milter-greylist has a default way of doing this and would do it for that list. That way I get a fresh list on upgrade without having to copy it by hand into my main config.

Cheers

    Elrond