Milter-greylist

True on the auto-reload, but it might be worth it for some -- if not,  
then they don't need to use includes.

Also, adding tuples would be nice, but I had a very capable scheme  
going where every 10 minutes, an IMAP mailbox named "block" would be  
polled, and any messages found in that mailbox would be parsed and the  
offending relay would be used to add a blacklist entry by IP address.  
For those servers that do retry and push through the greylist, this  
effectively blocks them after they've come through once. There is a  
manual step, but a minor one -- dragging a spam message into this  
mailbox does the deed automatically.

Without the ability to modify lists (not just tuples) directly, this  
isn't really workable for milter-greylist without lots of config file  
parsing/modifying, or using a template file or other options. With  
includes, this could be done by sending an interrupt to the milter- 
greylist process to reload, or directly with a CLI tool...

-Paul


> On Sep 11, 2009, at 2:51 PM, manu@... wrote:
> Paul Venezia <pvenezia@...> wrote:
> > Also, this could possibly be accompanied by adding support for file
> > include in the configuration file.
>
> File include tend to kill the ability to auto-reload on change.
>
> > Thoughts?
>
> I have been thinking about it for a while. The path of least  
> resistance
> would be to improve the mxsync protocol, and write a command line tool
> for sending commands to it.
>
> For now mxsync is just able to add greylist and autowhitelist tuples.
> Since the databases have been merged, now tuples have a type. You  
> could
> add blacklist tuples, and commands to remove tuples.
>
>