Milter-greylist

It is not as if we have to restart the daemon every 10 minutes.

I have 430 spams that passed through greylisting last 1 month. 400 of them is 
"Your wifes photo attached" virus or whatever. 


So just add a line to headers file when there is an outbreak and leave it be. 
Whenever the daemon is restarted, that virus would stop passing through once and 
for all.

Yes, this is for small environments. I used to get 50K+ spam a day, now I am 
down to 20 wife photos.

D



In my opinion, this is only acceptable for small environments. To
suggest a restart after changing only the configuration is too heavy.
Every restart is expensive because the greylisting DB has to be written
out to disk and read back in during startup. The interruption of the
service maybe to long, the peak I/O load of writing/reading the DB is
annoying.

As stated above, I would prefer to change the included file
and get the information provided to touch the main configuration file
forcing a read-in by the daemon ...

Otherwise, some technique using a communication socket/FIFO to talk
with the daemon comes to mind. Just an idea (no Manuel, I don't
have a patch for this already ;) ...)

Johann E. K.