Milter-greylist

We just put milter-greylist into production here.  It ran fine in
testing, but overnight it died

Jul 28 21:35:18 eric.servers.uwrf.edu sm-mta[19644]: j6T2ZFng019644:
milter_read(greylist): cmd read returned 0, expecting 5
Jul 28 21:35:18 eric.servers.uwrf.edu sm-mta[19644]: j6T2ZFng019644:
Milter (greylist): to error state
Jul 28 21:35:18 eric.servers.uwrf.edu mimedefang[2267]: envfrom:
Unable to obtain private data from milter context
Jul 28 21:35:18 eric.servers.uwrf.edu sm-mta[19644]: j6T2ZFng019644:
Milter: from=<rdaily@...>, reject=451 4.3.2 Please try
again later
Jul 28 21:35:19 eric.servers.uwrf.edu sm-mta[19644]: j6T2ZFng019644:
from=<rdaily@...>, size=0, class=0, nrcpts=0, proto=SMTP,
daemon=MTA, relay=pacific54.youroptinmail.com [130.94.133.60]
Jul 28 21:35:19 eric.servers.uwrf.edu sm-mta[19644]: j6T2ZFnh019644:
ldap dustin.i.williams@... => w1001702@...
Jul 28 21:35:29 eric.servers.uwrf.edu sm-mta[19647]: j6T2ZTkZ019647:
Milter (greylist): error connecting to filter: Connection refused by
/var/spool/MIMEDefang/milter-greylist.sock
Jul 28 21:35:29 eric.servers.uwrf.edu sm-mta[19647]: j6T2ZTkZ019647:
Milter (greylist): to error state


I suspect the culprit here is the envfrom: Unable to obtain private
data from milter context - which seems to have kicked off the death of
the milter.  Anybody got a clue on this?