I and a few others here have begun noticing that periodically Sieve won't filter a message properly. Sometimes I've even resent the message again to find that on that occasion it did get filtered just as expected. I wonder, could that BerkeleyDB leak for which Rob just posted those two patches have any bearing on this? Sadly, so far I haven't been able to detect a pattern to make this report more meaningful, but I'll keep an eye out.
-- Amos