Milter-greylist

I have a CentOS 6 server, running milter-greylist 4.2.7-1 from RPMforge, 
and try as i might, i can't seem to get it to acknowledge that successful 
STARTTLS has been observed:

Oct 17 14:56:26 buzz sendmail[32147]: STARTTLS=server, relay=mout.kundenserver.de [212.227.126.130], version=TLSv1/SSLv3, verify=OK, cipher=DHE-RSA-AES256-SHA, bits=256/256
Oct 17 14:56:26 buzz milter-greylist: s9HDuQFB032147: addr mout.kundenserver.de[212.227.126.130] from <SENDER> to <RECIPIENT> delayed for 00:10:00 (ACL 132)
Oct 17 14:56:26 buzz sendmail[32147]: s9HDuQFB032147: Milter: to=<RECIPIENT>, reject=451 4.7.1 Greylisting in action, please come back later
Oct 17 14:56:26 buzz sendmail[32147]: s9HDuQFB032147: from=<SENDER>, size=0, class=0, nrcpts=0, proto=ESMTP, daemon=MTA, relay=mout.kundenserver.de [212.227.126.130]

i'm not running the binary with the "-A" flag.  i've tried both with and 
without "racl whitelist tls /.*/" in my greylist.conf.  there are no other 
"auth or "tls" lines in my greylist.conf.  ACL 132 is my catch-all "acl 
greylist default delay 10m autowhite 150d", the last line of my 
greylist.conf file.

have i missed anything obvious?  how can i distinguish between "sendmail 
not passing the right information" and "milter-greylist not doing the 
right thing with it"?  can anyone suggest other checks i can do, or alleys 
i might explore?

thanks for any light anyone can shed!


   Tom Yates
   Cambridge, UK.