Milter-greylist

I installed milter-greylist about a week or so ago on a low-volume 
production machine (SuSE 9.0) for testing and am very satisfied overall. 
It just looks like I may have to stop it every now and then, so my bayes 
filter may acquire some new information. ;-)

I have a few questions which arose right after installing and configuring, 
but it took me some time to get on this list due to my blacklisting yahoo.
 
1. I'm getting an error 
Milter (greylist): error connecting to filter: Connection refused by 
/var/milter-greylist/milter-greylist.sock 
 
each time I restart the milter with the provided init script. As I heard 
in the meantime this is normal and I don't need to restart/reload the 
milter after configuration changes, so in the future I will rarely need to 
restart the milter. But I still wonder why this happens. I run a different 
milter on another machine which needs to get restarted to take 
configuration changes and there sendmail won't complain.
 
2. compiling with the latest libspf2 throws this linker error 
In file included from /usr/local/include/spf2/spf.h:27, 
                from spf.c:228: 
/usr/local/include/spf2/spf_server.h:23:30: spf_dns_internal.h: No such 
file or directory 
 
I installed libspf2 before compiling the milter. As it turns out the 
spf_dns_internal.h wasn't copied from the source directory to the lib 
includes by make install. It's not clear from your instructions on the 
website if one should install libspf2 or just use the headers in the 
source. I have just used headers from the source without installing in the 
past with other projects, but sometimes you get other linker errors 
because the files in the source may be arranged in a different hierarchy 
than how they get included. So, I think the preferrable method actually is 
to install them? I copied the file to where it was looked for and 
everything worked fine then. If it is a bug then it is a bug in the 
libspf2 install, of course. Nevertheless, I thought it's 
worth mentioning. 
 
3. I set the option "lazyaw". The tuples get still collected in 
greylist.db although only the IP should be relevant now. So, it's not 
clear if it uses IP only or the (IP, sender, recipient) tuple now. Same 
goes for the X-Greylist header, it still says "whitelisted by" all three, 
so it's not clear from there either. 
 
4. X-Greylist is adding quite a long text, it would be nice to have an 
option to either use templates for it or set a "short mode", f.i.: 
X-Greylist: Sender IP whitelisted 
X-Greylist: Delayed 00:30:00 
 
5. I set "greylist 10m", but the milter says "come back in 00:14:00". Is 
there a limit 
of 14 minutes or 4+config minutes? 


Kai

-- 
Kai Sch\ufffdtzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com