This is not really a bug but it definitely is a gotcha. Mailwasher Pro has a spam learning feature which was working okay until several weeks ago when it started to indicate obvious spam as needing to be designated as legitimate mail or spam. This is not critical since I use several methods of identifying spam but I do like the databases to vote the same way so I have a backup. I was mucking around the Mailwasher configuration today where I found a configuration parameter that limited the database size to 4 MB but the note attached to it recommended setting this parameter to 8 MB. I quickly checked my database size. Yes, I had already maxed out. I went back into Mailwasher and set it to 8 MB. Since then it has done a better job of identifying spam.