Milter-greylist

manu@... writes:

> Try upgrading flex as well?

No, simply forgot to do it.

> Build the beast with -g, make sure the binary is not stripped at install
> step, run it under gdb, and we'll have the source code where it crashes.

This is what I did when I was trying to reproduce with gdb `attached' to
the running process. gdb claimed he was unable to open y.tab.c ...

> I hope we can see some code I wrote in the yacc specification file,
> because if the problem occurs in the parser internals, it will be a
> nightmare to debug.

I am afraid I will have to add some debug print statements in order
to figure out where the code crashes.