Milter-greylist

in /etc/mail/greylist.conf
# It is also possible to whitelist sender
# machines using their DNS names.
#acl whitelist domain example.net
acl whitelist domain fakeaddwater.com


yet , in the maillog:
Nov  1 10:20:04 net milter-greylist: kA1IJs14014251: addr
313.00.313.20 from <Liz@...> to <scotts@...> delayed
for 00:03:00


Why didn't the email go straight through?

c.r.p. wrote:
> in /etc/mail/greylist.conf
> # It is also possible to whitelist sender
> # machines using their DNS names.
> #acl whitelist domain example.net
> acl whitelist domain fakeaddwater.com
> 
> 
> yet , in the maillog:
> Nov  1 10:20:04 net milter-greylist: kA1IJs14014251: addr
> 313.00.313.20 from <Liz@...> to <scotts@...> delayed
> for 00:03:00
> 
> 
> Why didn't the email go straight through?
> 

Because that whitelist applies to the name of the MACHINE that delivered it. Not
the domain name in the "mail from" command.

In this case, I assume you've hacked up log for privacy reasons, most notably
here the "addr" part, as 313.00.313.20 is not a valid IP address.

In any event, look at the real IP address and do a reverse DNS on it. If it does
not come back as something in "fakeaddwater.com", it won't match.

c.r.p. <shcv34c@...> wrote:

> yet , in the maillog:
> Nov  1 10:20:04 net milter-greylist: kA1IJs14014251: addr
> 313.00.313.20 from <Liz@...> to <scotts@...> delayed
> for 00:03:00
> 
> 
> Why didn't the email go straight through?

Because 313.00.313.20 does not have a reverse DNS, therefore it cannot
match your domain clause.

If you want to match against the sender e-mail address, use the "from"
clause. 
 
-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...