Hi, We've got milter-greylist working on 5 servers. Recently, we went from a whitelist default policy to a blacklist policy. A few weeks before, we realized that we didn't need to restart milter-greylist after each change to the config file, so we don't restart it after each change anymore. The problem is that it comes back to the default config, once in a while, w/o obvious reason. How can I tell? The default delay comes back to 30m (we're using 1m) "delayed for 00:30:00", also, we usually use the quiet option, but milter greylist starts saying 'come back in 30:00'. I thought, at first, that it was a syntax error in the config, but we're now checking the config file everytime we sync it, so it shouldn't be the case. Here is what I found in the logs: lots of : milter-greylist: greylist, mi_rd_cmd: read returned -1: Connection reset by peer A few of these: milter-greylist: Unexpected reply "105" from peer 10.20.20.50 closing connexion (0 entries queued) Anyone experiencing a similar problem? Thanks, Ugo
Message
milter-greylist 2.0.2 resetting to default automatically
2006-11-29 by Ugo Bellavance
Attachments
- No local attachments were found for this message.