Hi, just a couple quick little wish items....

1) Redirect logfile, quarantine and queue logging to another location
2) Cumulative inbound connection stat along with current
3) relay attempts stat (versus just showing a blocked email and nothing in quarantine)
4) ability to turn over logfile more than once per day (selector to rotate logfile every 1-24 hours)
5) Ability to rotate quarantine (new quarantine file every 15, 30, 45, 60... minutes) for easier management (reviewing large quarantine files for false positives is cumbersome)
6) Logfile for emails delivered from quarantine (false positive log essentially)
7) Ability to alter interval when white/ black lists are reloaded/reread. Every minute is great, but they are reloaded when changes are saved, based on this is evry minute too often?
8) Admin alert ability - with # of emails per minute etc threshold or something like that to warn of email attacks or storms.

This is an absolutely fabulous product, with excellent support. I would love it if there was an option to pay you guys extra for direct telephone support too!

Keep up the excellent work!

Wayne

Hi Wayne,

I'll add the comments below:

1) Redirect logfile, quarantine and queue logging to another location
It's in the very-very-near-future plans!

2) Cumulative inbound connection stat along with current
We've just added cumulative stats, having both cumulative and current session only is a bit farther out...

3) relay attempts stat (versus just showing a blocked email and nothing in quarantine)
We are placing all quarantine items in a database for the next release. This will allow us to create a web interface for end users to check their own quarantine. As a side effect, being in a database, it will allow admins to gather all sort of stats from it.

4) ability to turn over logfile more than once per day (selector to rotate logfile every 1-24 hours)
Added to wish list.

5) Ability to rotate quarantine (new quarantine file every 15, 30, 45, 60... minutes) for easier management (reviewing large quarantine files for false positives is cumbersome)
Let's go back to this one after the new quarantine has been released, to see how it performs

6) Logfile for emails delivered from quarantine (false positive log essentially)
Added to wishlist

7) Ability to alter interval when white/ black lists are reloaded/reread. Every minute is great, but they are reloaded when changes are saved, based on this is evry minute too often?
Good idea!

8) Admin alert ability - with # of emails per minute etc threshold or something like that to warn of email attacks or storms.
Added to wish list

Roberto
LogSat Software

We're trying to make the SQL code as compatible as possible so admins can choose the DB platform they prefer or are standarized on. We're currently developing for MS SQL, Access and Oracle.

Roberto
LogSat Software

That is great since on any given day I have 10,000-20,000 emails that are in quarantine.

While it takes some time to review them for false positives, my clients are very happy with not having to receive 100’s emails offering them a bigger penis. It is sad to think that the people that are sending out this trash think that we are so hung up on what hangs between men’s legs.

How about MySQL? I know it is close to SQL, but the open source nature of it compliments your price structure nicely for smaller organizations who want to use it. I wouldn't want you to remove your product as an option for small org's because of the backend requirements, unless you can log to a DB or the file system.  That said postgres too?

Yeap, again our goal is to make it as compatible and flexible as possible. We're going to use a user-selectable connection string (actually an Universal Data Link - .udl - file). The SQL statements we are using are as simple as we can make them for compatibility. We are currently developing and testing on MS SQL and Access. As soon as we have that ready and tested we'll most likely release a build with those features since many users are impatient are asking for this. Once that is done we'll see if any tweaks are needed for Oracle and MySQL (we hope none, but there seems to be a law that says there will be...) and add that in the following build.

Roberto
LogSat Software

Yeap, that will be in there with the next build as well.

Roberto
LogSat Software

Roberto,

Are your plans to REQUIRE the use of a backend database?

I can easily understand that many may require it, but for smaller sites, it would be an extra hurdle.

Great Product and Excellent Support!

Luis...

Luis,

Let me start by saying that we're trying to implement the new quarantine in such a way as to make it as simple as possible to use the backend database.

Our goals are (1) to have a very simple database (right now we've manage to keep it down to just three tables, with no stored procedures and other complications), and (2) to support as many platforms as possible transparently to the user. We're planning on testing with MS SQL, Access (free platform), Oracle and MySQL (free platform).

To anwer your question, no, SpamFilter will not require the use of a database. But in the new version, without a database the quarantine option will be disabled. We've thought about leaving two quarantines, one with the existing database-less functionality, and one with the new DB features, but decided against it. Double-functionality was much more prone to bugs and errors...

Roberto F.
LogSat Software