Re: [Sqlgrey-users] sqlgrey fails when configured with multiple machines

[Dan F. <da...@ha...>]

Karl O. Pinc wrote:
> On 07/06/2014 06:07:58 AM, Dan Faerch wrote:
>
> If someone was really worried about sqlgrey dying then there's
> probably a way to run it from inetd.  But that just pushes the problem of a
> dead daemon back to inetd, so the right thing to do is work from inittab.

Indeed.
I had issues with postgrey +10 years ago, before i switched to sqlgrey.
And i had based an internal policy-daemon upon that codebase as well.
Which then experienced the same problem and i simply couldnt track down
the bug.
Sometimes they would just stop responding, but they were still running.

I searched a long time for a way to configure the default
policy-daemon-response in postfix from "defer_if_permit" to "dunno", but
found nothing. I even stared at the source to postfix for a while, to see
if it was in there, as an undocumented option. I couldnt find anything to
suggest it.

So i ended up creating an ultra simple "policy-daemon-proxy", whos only
job was to talk to the real policy server, have faster timeout and always
report "dunno" if something goes wrong. A really silly hack and it just
underlines why this option should exist in postfix.

Then, i went with "sqlgrey" and all my problems disappeared ;)