While.org.uk - Re:Vispan 3.0 and access.db

While.org.uk

home | post reply | threaded view | help | rules

Boardwalk :: Forum List

Vispan

Running

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.

| | The administrator has disabled public write access.

Random
User

Senior Boarder

Posts: 11

Karma: 0

Re:Vispan 3.0 and access.db - 2007/05/26 19:00 The bad news is that Vispan 3.0 is NOT cleaning expired entries from /etc/access, so blocked IP's just keep accumulating.

I tested this on a clean mail server with Vispan set to keep naughty IP's for 15 minutes.

After nearly 2 hours, there are 4 entries in etx/access but only 1 entry left in Vispan spam list.

| | The administrator has disabled public write access.

jgoggan
User

Fresh Boarder

Posts: 3

Karma: 0

Re:Vispan 3.0 and access.db - 2008/04/01 19:53 Any more info on this old post? I just noticed that I am experiencing the same thing. I just checked and my Access file as 176 entries in it created by Vispan. But, Vispan shows only 97. That means that I have a lot of entries that are likely never going to fall out.

What is the best way to resolve this? Can I just delete ALL of the entries from the access file and let Vispan slowly rebuild them? But, if I do that, since Vispan already has 97 is its DB, it will likely not add those ones again, right?

So how can I fix it? Do I have to wipe the Vispan DB?

- John...

| | The administrator has disabled public write access.

Random
User

Senior Boarder

Posts: 11

Karma: 0

Re:Vispan 3.0 and access.db - 2008/04/12 19:25 Pretty sure that when I did a complete fresh install of everything, it worked OK.

So there may have been an OS file that needed an update, or something like that.

So Ver 3 is now working happily on a couple of Centos 5 servers that I use, though I still have V2.10 on an older remore WhiteBox 4 server - and this may be the reason - I really don't recall.

What OS are you using?

| | The administrator has disabled public write access.

Boardwalk :: Forum List Vispan Running

Joomlaboard Forum Component 1.1.3 Stable
Two Shoes M-Factory