Milter-greylist

> > > This tool could also be used to dump the db and stop the milter.
> >
> > I have this already in progress, though not done yet...
> >
> > It would be useful for me to know as to what other commands would 
be
> > useful to have.
> >
> > Things I have in mind currently are:
> >       * Ping daemon to see if alive or stuck

[gelgin@server gelgin]$ ps -clu spfmilt
F S   UID   PID  PPID CLS PRI ADDR SZ WCHAN  TTY          TIME CMD
5 S   100  6006     1 TS   23 -  2568 -      ?        00:00:00 milter-
greylist
1 S   100  6007  6006 TS   23 -  2568 -      ?        00:00:00 milter-
greylist
1 S   100  6008  6007 TS   24 -  2568 -      ?        00:00:00 milter-
greylist
1 S   100  6009  6007 TS   20 -  2568 rt_sig ?        00:00:00 milter-
greylist
1 S   100  6011  6007 TS   20 -  2568 rt_sig ?        00:00:00 milter-
greylist


> >       * Reconfigure

again if it sees a .db file change (like it does for greylist.conf) 
OR SIGUSR[12]


> >       * Force db dump
could accept a signal. set dump time to 0 ?

> >       * Clean shutdown of daemon

i thought it does a dump on SIGTERM ?


> >       * Increase/decrease debugging level
> >       * Stats, and these could be the following:
> >               * Current thread count

see above rt_sig is a thread.

> >               * Total number of connections to daemon

is this a problem ?. what would i infer from that # ??

> >               * Greylisted responses count
> >               * Whitelisted responses count

i'd still like for the non-priveleged user to be able to read .db 
file. why can't grey milter preserve it's [u]mask on dump ?? [seems 
like a 2-3 line code change]

> >               * Greylisted entries
> >               * Whitelisted entries

alias ts='tail -2 /var/milter-greylist/greylist.db'

> >               * Expired count
> >               * ...
> >
>

personnally i think this 'tool' is overkill. just want to to perl awk 
grep my way to ? for example i thought about building a per/user 
barchart of greylisted entries [to see which users are getting 
hammered] see for example :

http://www.exgig.com/spam.cgi

sorry i still think rereading greylist.db if it's changed is a good 
idea. as someone pointed out on 'serious' parse error it reverts 
which is also a good idea.

-george