Kai Schaetzl <maillists@...> wrote: > 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.) Can you provide the patch for that? > 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? Probably. :-) > I also noticed that the T option doesn't seem to override the options in > greylist.conf, while the others do. It should. Do you contribute the fix? (that's an easy one) -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu@...
Message
Re: [milter-greylist] A few questions
2005-12-10 by manu@netbsd.org
Attachments
- No local attachments were found for this message.