Milter-greylist

Ethan Burnside <burnside@...> wrote:

> Yea, I grabbed 1.3.4 last night and put it on our cluster of 5 or so
> mail servers.  (somewhat of a forced upgrade... we were in desperate
> need of the dumpfreq setting)  We have the greylist.conf auto generated
> from a database every time someone changes their settings from a
> web-based interface.  We also monitor the processes on all 5 of these
> mail servers to make sure all the necessary processes are running all of
> the time.  I can reliably go into the web interface, make a change, and
> minutes later all of our mail servers are red on the monitor and paging
> us, angry that milter-greylist is no longer running.  ;-)  While I don't
> recall 1.2.2 crashing all at once like this, it hadn't been particularly
> reliable either, so we've just kind of got used to having a cron job
> setup to restart it periodically.

Obviously there is something horribly wrong with the configuration
parser. The temporary workaround is simple: restart milter-greylist once
you changed the configuration file.

Is someone able to provide me an access to a system where the crash can
be reproduced reliabily? It's hard for me to track down bugs that I
can't see.

Anyway... Nice setup you have. Would you like to write a web page about
it? We could have a milter-greylist success-stories page.

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...