> I don't see where the problem is. I have to think that's not the file it's really using, or there's a second filter policy file configured. Or I suppose there's some weird config parsing issue, so if you can reproduce on 2.4, we can certainly take a bug report if that same file produces that error. -- Scott