Milter-greylist

Hi,

    We were experiencing this with 2.0.2 and we just upgraded to 3.0.1
and we are still seeing it.

    I thought that milter-greylist was supposed to re-read its config
file automatically and ajust (and I can see the reload log entry). 
Should we come back to the old method of restarting milter-greylist
after editing greylist.conf?  We have a few servers that  are MXSYNCs
so what I usually do is edit the file on one server, then I run a
script that

- does a milter-greylist -c
- tests the return value
- if it is not equal to 0, it exits with an error message
- if it is zero it copies greylist.conf to the other servers
- it does a milter-greylist -c on each other servers and tests the
return value.

Is there something wrong with my procedure?

Regards,

Ugo