Spam Filter ISP Support Forum

  New Posts New Posts RSS Feed - Questions about new Enterprise beta
  FAQ FAQ  Forum Search   Register Register  Login Login

Questions about new Enterprise beta

 Post Reply Post Reply
Author
dcook View Drop Down
Senior Member
Senior Member
Avatar

Joined: 31 January 2005
Location: United States
Status: Offline
Points: 174
Post Options Post Options   Thanks (0) Thanks(0)   Quote dcook Quote  Post ReplyReply Direct Link To This Post Topic: Questions about new Enterprise beta
    Posted: 26 December 2006 at 1:32pm

We are testing the enterprise beta on a test server and have a few questions related to our setup.


1) AutoWhitleListForceDelivery import:    

Upon installation and switching to enterprise mode we copied all the settings from our standard mode filter files.  We are using MySql 5 we do not see any entries in the database 'tblwl_autowhitelistforcedelivery' table after import.  We assume that this is the autowhitelist from forwarded delivery.  Should it have copied the data from the original text file?  Is the autowhitelist text file data supposed to be imported into the database?

(The original txt file seems to be mapped correctly in Drive:\spamfilter\domains\SFI\Filters.ini.)


2) AutoWhitleListForceDelivery function in Enterprise mode:

Our Current Setup:

For previous versions and Standard Mode we have created a service that synchronizes a AutoWhitleListForceDelivery text file (AutoWhitleListForceDelivery.txt) with a customer database table. This service syncs data to/from the AutoWhitleListForceDelivery.txt  text file to the database table and allows the database table to be authoritative for spamfilter installations. The data is in the following format in out current AutoWhitleListForceDelivery.txt file:

fromemail@example.com|toemail@example.com

For the data table we store the data in 'EmailFrom' and 'EmailTo' fields which is similar to the AutoWhitleListForceDelivery file format.

In addition, we also have have a Web user interface that allows for users to add AutoWhitleListForceDelivery email addresses to the custom data table mentioned above - which is replicated by our custom service. In the process of creating an entry they enter a 'EmailFrom' value and that is stored in the data table along with their 'EmailTo' address.


Questions:

A) Does the enterprise AutoWhitleListForceDelivery function match the end result functionality of our 'current setup' above?

B) Does the 'import' function imply that the use of the current 'AutoWhitleListForceDelivery.txt' is obsolete?

C) What kind of changes would we need to make to our Web user interface to allow users to manage their own white list that matches the functionality we have described above?


3) 'AuthorizeTo' list in Enterprise mode:

Our Current Setup:

To use and maintain a current AuthorizeTo list we use a service to copy EmailTo aliases from our primary e-mail servers SQL database and we write them to the AuthorizeTo list file - AuthorizeTo.txt.


Questions:

A) In enterprise mode, will our current setup work above work and copy data from the file to the database when the file changes?

B) Does the 'import' function imply that the use of the current 'AuthorizeTo.txt' is obsolete?

C) If not, should we synchronize the AuthorizeTo data from our primary e-mail server  directly to the 'tblwl_authorizedtoemails' table?

4) For quarantined e-mail have their been any changes to the way an entry is delivered or expired?

The current setup requires setting the 'Deliver' or 'Expire' fields to a +/- 1 to deliver or expire respectively. 


Thanks,

Dwight
www.vividmix.com
Back to Top
LogSat View Drop Down
Admin Group
Admin Group
Avatar

Joined: 25 January 2005
Location: United States
Status: Offline
Points: 4068
Post Options Post Options   Thanks (0) Thanks(0)   Quote LogSat Quote  Post ReplyReply Direct Link To This Post Posted: 26 December 2006 at 11:19pm
Originally posted by dcook dcook wrote:

We are testing the enterprise beta on a test server and have a few questions related to our setup.


1) AutoWhitleListForceDelivery import:    

Upon installation and switching to enterprise mode we copied all the settings from our standard mode filter files.  We are using MySql 5 we do not see any entries in the database 'tblwl_autowhitelistforcedelivery' table after import.  We assume that this is the autowhitelist from forwarded delivery.  Should it have copied the data from the original text file?  Is the autowhitelist text file data supposed to be imported into the database?

(The original txt file seems to be mapped correctly in Drive:\spamfilter\domains\SFI\Filters.ini.)

That is (was...) caused by a typo in the code.... I say "was" because the impact of that was so big, and the solution so simple, that we've just re-uploaded a new beta as v3.5.3.631.

Originally posted by dcook dcook wrote:


2) AutoWhitleListForceDelivery function in Enterprise mode:

Our Current Setup:

For previous versions and Standard Mode we have created a service that synchronizes a AutoWhitleListForceDelivery text file (AutoWhitleListForceDelivery.txt) with a customer database table. This service syncs data to/from the AutoWhitleListForceDelivery.txt  text file to the database table and allows the database table to be authoritative for spamfilter installations. The data is in the following format in out current AutoWhitleListForceDelivery.txt file:

fromemail@example.com|toemail@example.com

For the data table we store the data in 'EmailFrom' and 'EmailTo' fields which is similar to the AutoWhitleListForceDelivery file format.

In addition, we also have have a Web user interface that allows for users to add AutoWhitleListForceDelivery email addresses to the custom data table mentioned above - which is replicated by our custom service. In the process of creating an entry they enter a 'EmailFrom' value and that is stored in the data table along with their 'EmailTo' address.


Questions:

A) Does the enterprise AutoWhitleListForceDelivery function match the end result functionality of our 'current setup' above?

The functionality of the AutoWhiteListForceDelivery has not changed in the new SpamFilter 3.5 (both Standard and Enterprise). That has changed is only the fact that in the Enteprise version, this whitelist, as with most other black/whitelists and settings, are now stored in the database.

Originally posted by dcook dcook wrote:



B) Does the 'import' function imply that the use of the current 'AutoWhitleListForceDelivery.txt' is obsolete?

For SpamFilter Enteprise this is correct. In SFE all settings are now stored in the database. SFE will automatically export those settings to text files, and will actually use those text files to read its filter settings. However this (reading settings from text files) is done only so that we can maintain 100% uptime in case the database goes offline. The database however is still the authoritative source of data. As soon as the data in the database tables is changed, SpamFilter will immediately see the change, and export the data to the relative text file. Your should thus avoid making any changes to the text files in SFE, as those changes will be lost as soon as the databse is changed.

All the above is only valid for SFE. In SFI 3.5, nothing changes from SFI 3.1.

Originally posted by dcook dcook wrote:



C) What kind of changes would we need to make to our Web user interface to allow users to manage their own white list that matches the functionality we have described above?

Your web interface should make changes directly to the relative table in the database. We tried to keep as much as possible the same schema for the records as the one in the old text files. Any time you make a change to the database (INSERT/DELETE/UPDATE), SpamFilter will automatically see it within a few seconds (around 5), and will update its working files. You can even make the changes if SpamFilter is not running.... SpamFilter will see them the next time it's started. This is because we make use of triggers in the database that cause all changes to be logged in temporary tables so SFE will see them...

Originally posted by dcook dcook wrote:


3) 'AuthorizeTo' list in Enterprise mode:

Our Current Setup:

To use and maintain a current AuthorizeTo list we use a service to copy EmailTo aliases from our primary e-mail servers SQL database and we write them to the AuthorizeTo list file - AuthorizeTo.txt.


Questions:

A) In enterprise mode, will our current setup work above work and copy data from the file to the database when the file changes?

B) Does the 'import' function imply that the use of the current 'AuthorizeTo.txt' is obsolete?

C) If not, should we synchronize the AuthorizeTo data from our primary e-mail server  directly to the 'tblwl_authorizedtoemails' table?

All the answers relative to the AutoWhiteListForceDelivery discussion apply tho the "AuthorizedTO" filter as well (and all the other black/white lists).

Originally posted by dcook dcook wrote:



4) For quarantined e-mail have their been any changes to the way an entry is delivered or expired?

The current setup requires setting the 'Deliver' or 'Expire' fields to a +/- 1 to deliver or expire respectively. 

If there are changes, they are not intentional and would qualify as bugs


Roberto Franceschetti

LogSat Software

Spam Filter ISP
Back to Top
dcook View Drop Down
Senior Member
Senior Member
Avatar

Joined: 31 January 2005
Location: United States
Status: Offline
Points: 174
Post Options Post Options   Thanks (0) Thanks(0)   Quote dcook Quote  Post ReplyReply Direct Link To This Post Posted: 29 December 2006 at 12:24pm
Thanks for the answers Roberto.  We are excited to see this new version launch next year.  Also Happy New Year to you and yours! 
Dwight
www.vividmix.com
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down



This page was generated in 0.094 seconds.