This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
how_to:exceptions [2013/05/08 11:57] – [Exceptions] paul | how_to:exceptions [2013/05/08 11:58] – [VPOP3 2.6 and earlier] paul | ||
---|---|---|---|
Line 4: | Line 4: | ||
=====Common causes===== | =====Common causes===== | ||
- | =====VPOP3 2.6 and earlier===== | + | ====VPOP3 2.6 and earlier==== |
In VPOP3 2.6 and earlier it was quite common for there to be database corruption problems with the SQLite database which was used in those versions. | In VPOP3 2.6 and earlier it was quite common for there to be database corruption problems with the SQLite database which was used in those versions. | ||
Line 12: | Line 12: | ||
If it contains the text: | If it contains the text: | ||
- | * **In Bayes Sync Processor** - this usually means that the VPOP3\_database\spamfilter.db database is damaged. Stopping VPOP3, and restoring a copy of that file from you latest backup is the best solution. If you are not doing backups, then deleting that file instead, and then restarting VPOP3, will make VPOP3 start a new database from scratch. You will not lose any critical information by doing this, but the spamfilter may not be as effective as before for a while | + | * **In Bayes Sync Processor** - this usually means that the VPOP3\_database\spamfilter.db database is damaged. Stopping VPOP3, and restoring a copy of that file from your latest backup is the best solution. If all your recent |