setting up a new spamd plus various content filtering at a client site we were kind of baffled to see that apparently manually setting an address to TRAPPED with spamdb, ie
spamdb -a -t 211.49.57.32 for some reason seems porous, in that messages received from that IP address still hits the content filter a few minutes after the manual intervention. I just wonder what it is I'm seeing here - spamdb lookups cached or something? - Peter -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
