Milter-greylist

> * 1 Thread 285b99c0 (LWP 100145)  0x0804ca90 in real_eom (ctx=Cannot 
> access memory at address 0xbf000008
> ) at milter-greylist.c:918
> Cannot access memory at address 0xbf000004
> 
> up just results in: Cannot access memory at address 0xbf000004

Alright, in an attempt to make some progress I tried using the 
milter-greylist dev tree ( 4.3.8 ). This has got the proper

if (priv->priv_dkimstat != DKIM_STAT_OK) {

on line 151 there, and the milter does not crash. So, I assume whatever 
has changed outside dkimcheck.c makes the difference. That being said
stepping through dkimcheck_header/dkimcheck_validate and dkimcheck_error

priv->priv_dkimstat stays:

priv_dkim = 0x287eb600, priv_dkimstat = 0

through out stepping through. The result with 4.3.8 is that header or
not, the dkim pass ACL matches every time. I added some debug printing
to dkimcheck_error like so (for each case): 

 case DKIM_STAT_NOSIG: 
                mg_log(LOG_DEBUG, "DKIM failed: %s",
                       dkim_getresultstr(priv->priv_dkimstat));

                retval = SMFIS_CONTINUE;
                break;

Logging results in:

Sep 10 05:35:23 nyima milter-greylist: DKIM: Pass

So, now that we know line 151 isn't causing this to fail where should I 
poke around next? It still seems that there is either a misinterpreted 
return value or a default (pass?) is just plain untouched.

John