On 7/24/09 3:03 PM, Peter N. M. Hansteen wrote:
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?
It happened to me also with servers with huge white/black lists. If it's
happening for new connections, ensure that pf is configured with enough
maximum table entries (set limit table-entries).
