Spam Filter ISP Forums : New SpamFilter Enterprise beta v3.5.3.650

New SpamFilter Enterprise beta v3.5.3.650 : Door #2.SpamFilter will treat...

Tue, 08 May 2007 16:11:29 +0000

Author: LogSat
Subject: 5981
Posted: 08 May 2007 at 4:11pm

Door #2.

SpamFilter will treat headers just like as if they were part of the body. So most likely your keyword would say:
X-SF-BYPASS=TRUE

New SpamFilter Enterprise beta v3.5.3.650 : {TODO -cNew : Added "ScanAllHeaders"...

Tue, 08 May 2007 13:05:46 +0000

Author: WebGuyz
Subject: 5981
Posted: 08 May 2007 at 1:05pm

{TODO -cNew : Added "ScanAllHeaders" option in SpamFilter.ini file to also scan all headers for keywords}

How do i use this after setting the parameter in the ini file?

Do I do it like when using subject?
i.e. IF I add this to my blacklist keywords

X-SF-BYPASS=TRUE

or is it just looking for the existence of the header X-SF-BYPASS and not care about the variable?

Thanks!!

New SpamFilter Enterprise beta v3.5.3.650 : We do try to make things simple ...

Mon, 26 Feb 2007 08:56:29 +0000

Author: LogSat
Subject: 5981
Posted: 26 February 2007 at 8:56am

We do try to make things simple

New SpamFilter Enterprise beta v3.5.3.650 : Ok, I don't know how you...

Mon, 26 Feb 2007 08:32:20 +0000

Author: caratking
Subject: 5981
Posted: 26 February 2007 at 8:32am

Ok, I don't know how you did it without a DB change... but it seems to work somehow. I setup a second test box. I make keyword changes on one domain, and a little bit later the second server sees it and updates itself.

Neat!

Edited by caratking

New SpamFilter Enterprise beta v3.5.3.650 : we didn't want to alter the...

Sat, 24 Feb 2007 22:05:16 +0000

Author: LogSat
Subject: 5981
Posted: 24 February 2007 at 10:05pm

we didn't want to alter the DB structure to address the multiple servers issue. We always try to minimze any database changes to avoid causing upgrade problems to the users. The few times we do make DB changes, so far we've always made SpamFilter smart enough to recognize the different structure, and automatically make the DB changes on the fly. In this case, we used a programming workaround to take care of multiple changes, we did not have to modify the DB structure.

In regards to the lower case issue, SpamFilter converts the scripts into lower-case before executing them. If you manually execute the scripts within MySQL, then yes, you will run into a case issue. We'll be taking care of that in the near future, thanks for the reminder!

New SpamFilter Enterprise beta v3.5.3.650 : I updated the files included in...

Sat, 24 Feb 2007 18:04:05 +0000

Author: caratking
Subject: 5981
Posted: 24 February 2007 at 6:04pm

I updated the files included in the download, however I did not redo the database structure. I looked at the database create scripts and I notice two things:

1) I don't see any change to handle the multiple server issue (perhaps I missed it)

2) The mysql scripts are creating things using mixed case. Because of the unix mysql case restrictions I thought things were changed in the code to all lower case.

New SpamFilter Enterprise beta v3.5.3.650 : Thanks, I'll check it out....

Thu, 22 Feb 2007 22:39:35 +0000

Author: caratking
Subject: 5981
Posted: 22 February 2007 at 10:39pm

Thanks, I'll check it out. I don't actually need that feature currently as I've only got one beta machine running but it would be nice to see it work anyway.

New SpamFilter Enterprise beta v3.5.3.650 : caratking,We just released a new...

Thu, 22 Feb 2007 22:19:38 +0000

Author: LogSat
Subject: 5981
Posted: 22 February 2007 at 10:19pm

caratking,

We just released a new beta, 3.5.3.651, that attempts to solve the issue below.

caratking wrote:

Has the issue of changes to configuration files being updated on all servers be addressed yet?

The last time I checked, when a new domain (for example) was added it would trigger an update to the server(s). However, there was currently no tracking so the first server who checked in would get the updates and any other servers would not know to update.

ight now, I believe they are just tossed.

New SpamFilter Enterprise beta v3.5.3.650 : Ultimately, SpamFilter Enterprise...

Thu, 22 Feb 2007 16:14:21 +0000

Author: LogSat
Subject: 5981
Posted: 22 February 2007 at 4:14pm

Ultimately, SpamFilter Enterprise will look at changes in the text files. However the authoritative source is always the database. Any change in the database will automatically result in the creation of a new text file, which will overwrite the the old one.

In SFE, things work like this:
Any change in the database, whether SpamFilter is running or not, will cause that change to be logged in the table tblreloadinfo. SpamFilter continuosly monitors that table every 5 seconds. As soon as a change is detecte in the DB, SpamFilter will take the contents of the modified table, and dump it to the corresponding text file. SpamFilter will then import the contents of that text file.

This was done (SpamFilter importing the local text files) so that if the database is not available for some reason, all the config data is still available to SpamFilter, even if you have to stop/start SpamFilter while the DB is offline.

So the *moral* is that with SFE you should only modify the entries in the database.

The new SpamFilter 3.5 SFE can only be configured to run in "SFI" mode, so that you can still have all the new features and fixes, but still have the file-based filters. You will however loose the "Enterprise" feature that allows you to customize each filter for each domain.

New SpamFilter Enterprise beta v3.5.3.650 : Can someone clarify for me: When...

Thu, 22 Feb 2007 15:21:47 +0000

Author: jerbo128
Subject: 5981
Posted: 22 February 2007 at 3:21pm

Can someone clarify for me:

When using SFE, what does the server "watch" for changes: the .txt files, the database, or both?
We are using asp pages to modify the database in SFI, and thus am wondering just how much we need to change in the scripts before we move to SFE

Thanks for the help.