Milter-greylist

> Because the rules above are using client_addr, it uses the IP address for
> a match in access-db!
> 
> You have to state the ip address in access-db ...
> 
> Connect:1.2.3.4 OK
> 
> (OK, RELAY, WHITE tells milter-greylist to whitelist the IP) - use WHITE
> to prevent side-effects (not allowing any relaying to foreign hosts).
> 
> For a simple fix, change client_addr to client_name
> which contains the hostname or in case this isn't resolveable [a.b.c.d]
> for IPv4 or something like this [IPv6:2a02:c207:2011:3138::1] for IPv6
> addresses.
> 
> This checks the address and if not found the hostname against access-db
> ...
> 
> SLocal_check_rcpt
> R$+ $: $(storage {greylist} $) $&{client_addr}
> R$+ $: $>A <$1> <?> <+Connect> <$1>
> R<?> <$+> $: <?> $&{client_name}
> R<?> $+ $: $>A <$1> <?> <+Connect> <$1>
> R<$+> <$*> $: $(storage {greylist} $@ $1 $) $1
> 
> Regards,
> 
> Johann K.

Thank you!
I tried your config code above and made some progress.

Connect:example.com WHITE

With the WHITE keyword, my server responded with "reject=553 5.3.0 WHITE”, so I changed to OK.

Connect:example.com OK

That didn’t yield an error, but it wasn’t picked up by milter-greylist, so instead I tried:

Connect:complete.hostname.example.com OK

THAT did work, finally ML reported "X-Greylist: Message whitelisted by Sendmail access database, not delayed”. Great!
Too bad I didn’t work with domain name only, that makes this feature pretty useless.

I think I’ll return to whitelisting within greylist.conf

…unless someone with mad m4 skills has another suggestion to try! :)


- ME