Random
User
Senior Boarder
| Posts: 11 |   |
Karma: 0
|
Vispan 3.0 and access.db - 2007/05/26 16:56
After getting a few complaints about blocked email, I noticed a couple of entries in access.db that weren't in Vispan Spam list.
Further investigation revealed that while the Spam list had 86 entries, access had 598 all from Vispan.
So I manually matched them all up and deleted the excess from access.
However, just watching the system, it appears that Vispan is only updating access.db after new entries are added. I just noticed an entry removed from access, but the time stamp on access indicates no change. It did change when an entry was added though.
So apart from it not updating access.db after removing entries from access, I am curious if it is removing entries properly due to the huge number of excess entries that had accumulated.
Going to do some more tests.
|
Forum 
