Milter-greylist

> I have "lazyaw" in my greylist.conf and would have expected the second
> connection below not to be delayed since it's from the same server but
> it still was.
> 
> May 23 00:01:43 sun2 milter-greylist: q4MM1dxL010320: addr
> mail4.trafikverket.se[188.121.65.205] from =foo.bar@...>
> to <foo@...> delayed for 00:01:00 (ACL 370)
> May 23 00:01:43 sun2 sendmail[10320]: q4MM1dxL010320:
> from=<prvs=048936c67e=foo.bar@trafikverket.se>, size=17632, class=0,
> nrcpts=0, proto=ESMTP, daemon=MTA, relay=mail4.trafikverket.se
> [188.121.65.205]
> 
> May 23 00:45:20 sun2 milter-greylist: q4MMjF9Q016052: addr
> mail4.trafikverket.se[188.121.65.205] from =foo.bar@...>
> to <foo@...> delayed for 00:01:00 (ACL 370)
> May 23 00:45:20 sun2 sendmail[16052]: q4MMjF9Q016052:
> from=<prvs=048936c67e=foo.bar@...>, size=18917, class=0,
> nrcpts=0, proto=ESMTP, daemon=MTA, relay=mail4.trafikverket.se
> [188.121.65.205]
> 
> Also note that the from address is some generated one that
> milter-greylist logs incorrectly. The unique from address is what
> makes normal autowhitelist not trigger either which I understand but
> lazyaw should, right? Am I missing something here?
> 

Probably you do not have the recipient "foo@..." you
have masked the original recipients for privacy reason.
But the original recipients are the same
on the two set of syslog entries?
Because that must be the case for the whitelisting to work.