whitelists clients still being greylisted

[Dan Langille]

On 6 Nov 2006 at 9:13, LI Xin wrote:

> Dan Langille wrote:
> > Hi folks,
> > 
> > I'm setting up spamd with pf, and I'm finding that whitelisted IP 
> > addresses are still being greylisted.  For example:
> 
> Er?  Have you mounted fdescfs as /dev/fd?  I think this should be
> documented.

Hmmm, this is interesting... it is still greylisting that client.

My rules look right:

# pfctl -s nat
No ALTQ support in kernel
ALTQ related functions disabled
rdr pass inet proto tcp from <spamd-mywhite> to 64.147.113.42 port = 
smtp -> 127.0.0.1 port 25
rdr pass inet proto tcp from <spamd> to 64.147.113.42 port = smtp -> 
127.0.0.1 port 8025
rdr pass inet proto tcp from ! <spamd-mywhite> to 64.147.113.42 port 
= smtp -> 127.0.0.1 port 8025
# host 64.147.113.42
42.113.147.64.in-addr.arpa domain name pointer nyi.example.org.


# pfctl -t spamd-white -T show
No ALTQ support in kernel
ALTQ related functions disabled
   12.152.184.25
   66.35.250.206
   205.150.199.217
   216.136.204.119
# pfctl -t spamd-white -T show  | grep 205.150.199.217
No ALTQ support in kernel
ALTQ related functions disabled
   205.150.199.217
# host m21
m21.example.org has address 205.150.199.217
#

So why does m21 continue to be greylisted?

For those wondering, I've changed the domain name to example, the 
rest is real.

-- 
Dan Langille : Software Developer looking for work
my resume: http://www.freebsddiary.org/dan_langille.php