You may wish to set Bayesian filtering to "monitor" until you get it under control.
Go through your spam and not spam folders and be sure each has appropriate messages for Bayesian training. If a user sent spam be sure you remove those spam messages from the not spam folder and rebuild the db. White listing would not hurt in your case as those messages that were incorrectly identified would be placed in your not spam folder for future Bayesian training. You could clear the Bayesian table of your MySQL database, but i would just white-list to gather more non spam messages and then rebuild. On 7/23/2015 3:09 PM, Jay wrote: > Hey all. I have a question. Recently I have noticed that the spam filter > has been blocking emails that otherwise would seem legitimate. So for > instance I see a lot of weird behavior from the blocked report: > > spam reason: (Bayesian) [I need a quote for laminate flooring install in > Lakeland FL] > spam reason: (Bayesian) [Inv 5895] > spam reason: (Bayesian) [Invoice 10735] > spam reason: (Bayesian) [Aflac Policyholder Services Email Address > Verification Required] > spam reason: (Bayesian) [Payment Confirmation for Support] > spam reason: (Bayesian) [Your Progressive auto quote confirmation] > > These are just a few examples I found. There are others from banks, > insurance companies, customers, payroll services etc. Looking at some of > the emails that got blocked it doesn't seem to me that they should have. > If I use the built in analyzer ASSP thinks they are spam. I know I can > just whitelist these, but if the users don't inform me or they don't > check the blocked report on a daily basis they have no idea. We have the > spam filter set up that if a email gets rejected it sends a response > email back to the user with instructions on how to get safe listed. > Basically they contact an email address at my office that is unfiltered > and request to be whitelisted. The biggest issue we deal with is that > either the originating email address is a unmonitored email address or > the user just ignores it. I know I will run into this from time to time > still, but what concerns me is that our spam database is poisoned and > flagging emails that would have otherwise gone through previously. It > seems within the last 2 months this issue has cropped up. We did have an > issue where one of our users email got compromised and sent out spam. So > I am thinking this is where the issue started and poisoned the spam > database. > > We currently use MYSQL as the database for the spam database. Is there a > easy way to just wipe the database clean and start over from a previous > spamdb file? Is this as easy as just grabbing the spamdb from one of the > ASSP installations and dropping it into the import folder for MYSQL? Or > is this the case where I have to purge the database in MYSQL and > recreate it fresh. Any help/advice is greatly appreciated. Thanks. > > > ------------------------------------------------------------------------------ > _______________________________________________ > Assp-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/assp-user ------------------------------------------------------------------------------ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
