Milter-greylist

I can answer question 1 and 5 myself.

1. I assumed the milter was really getting started since the start script 
says so. Actually, after a restart it is dead. So there's no socket to 
connect to. It seems that the stop start sequence in the init script is 
too fast. It works after inserting a sleep 2. (Didn't try sleep 1.)

2. The Suse init script contains options values that override the 
greylist.conf:
OPTIONS="-T -L 24 -w 14m -P $pidfile -u $user -p $socket"
This should be changed to:
OPTIONS="-P $pidfile -u $user -p $socket" which is equivalent to what the 
other init scripts do. Or, even better, all of this should be fetched from 
greylist.conf, shouldn't it?
I also noticed that the T option doesn't seem to override the options in 
greylist.conf, while the others do.

Kai

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