Print Page | Close Window

autowhitelistdelivery broken in SFE

Printed From: LogSat Software
Category: Spam Filter ISP
Forum Name: Spam Filter ISP Support
Forum Description: General support for Spam Filter ISP
URL: http://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=6011
Printed Date: 24 October 2017 at 12:01am


Topic: autowhitelistdelivery broken in SFE
Posted By: WebGuyz
Subject: autowhitelistdelivery broken in SFE
Date Posted: 25 March 2007 at 2:02pm

caratking brought it up in another thread (see below) but this is a show stopper for us. When a message is removed from quarantine and we use individual filters (for all our domains) the entry is added to the correct domains WL_AutoWhiteListForceDelivery.txt file, but never updates the db. So if you stop/start SFE, that entry is GONE because there was never a db entry written.

Please fix this as soon as possible as we can't proceed without it working. Thanks!

While I'm bitching  I want to say I think the concept of being able to define 'Use Default' for each of the other lists is quite important as it becomes a nightmare to keep updated common keywords and blacklisted IP's. Right now I'm working on scripts to sync up changes from default to all 300 domains and then it occured to me I need to do the same for deletes. If I only had to worry about one table, the default table, it would be more logical. Not sure if something like this can wait until 4.0. If someone have a couple thousand domains this would become problemetic without being able to use defaults for common lists like BL keywords, BL ip's, RBL's, SURBL's, etc.

 

Originally posted by caratking caratking wrote:

Inb SFE, when you look through the Quarantine messages, and select Deliver Selected the system adds the email pair for auto whitelisted.

Is it also supposed to report back to the DB and add that pair (I see there is a table for it), and then sync with all the other servers?

My autowhitelist table is empty.



-------------
http://www.webguyz.net



Replies:
Posted By: caratking
Date Posted: 25 March 2007 at 8:49pm
You are not running beta software in a production environment with 300 domains are you?  That would be crazy.


Posted By: WebGuyz
Date Posted: 25 March 2007 at 9:23pm

Originally posted by caratking caratking wrote:

You are not running beta software in a production environment with 300 domains are you?  That would be crazy.

 

No, copied my production SFI directory to a test server trying it out. Since I want to have a separate autowhitelistdelivery file and authorizedto list for each domain I'm forced to make each of the domains a custom domain. I've only made a few custom domains for testing and evaluating  as I have to write scripts to split up the SFI authorizedto list into separate domains as well as the autowhitelistdelivery file. I thought I had 34000 entries but it is actually 340000 entries. Have to parse the list and add the right domain info into the tables.

 Until some of the duplication of the common data like keywords, suble, rbls can be consolidated by SFE to use defaults I may have to hold off a bit. Don't want to write scripts to duplicate common data across all domains and have to remove them later. Too much work ...



-------------
http://www.webguyz.net


Posted By: LogSat
Date Posted: 26 March 2007 at 12:16am
We agree on the severity of the AutowhitelistForceDelivery bug in the RC candidate, so we uploaded a patched RC2 already that includes all the latest fixes (see beta page for more details).
In regards to the "Use Defaults" issue, please note that with a button click you can copy *all* the settings from any one domain to any other domain. So if you add a new domain, it takes literally one click to customize all its settings by copying the defaults from the "ALL DOMAINS" for example.

...however as usual, if we misunderstood the problem, let us know!


-------------
Roberto Franceschetti

http://www.logsat.com" rel="nofollow - LogSat Software

http://www.logsat.com/sfi-spam-filter.asp" rel="nofollow - Spam Filter ISP


Posted By: WebGuyz
Date Posted: 26 March 2007 at 1:37am

Yeah, I can go ahead and copy the 'all domains' 300 hundred times via the gui, The problem I have is there are 300 hundred copies of the same data that is common to all our domains (like BL keywords). If I want to add a keyword to all 300 domains I have to write a script to copy it to 300 domains. If I want to remove a RBL because its no longer in service, I have to write a script to remove it from 300 domains.

If each of my 300 domains was totally unique and did not share common lists like BL keywords, etc, there would be no issue. But if I have to have the same entries, why duplicate them? Let them share entries in ALL DOMAINS and then add whatever uniques entries as needed for individual domains. That way I can add a single bl keyword to ALL DOMAINS table and that will take care of all 300 domains

 What if I had 2000 domains, I can imagine the size of the db if you had dupes of each common bl/wl x 2000.

But since no one else seems to feel this is an issue, maybe I'm beating a dead horse. If the autowhitelistdelivery is fixed I guess I'll get the update and just write my scripts to update all the domains whenever I want to add a keyword or blacklist an IP. There is no easy way to add a single keyword to all the domains via the gui if your using unique bl/wl for each domain.

Thanks!



-------------
http://www.webguyz.net


Posted By: LogSat
Date Posted: 26 March 2007 at 4:54pm
uhm... we'd think that it would be better (easier to understand, more manageable) to have the current conditions where, if you need to customize a domain, then all entries for that domain are unique, without inheritance. If an admin needs to make a global change, that can always be done by manipulating the data in the database directly with a SQL script. We do however see your point now in having "inheritance". Let us go live with SFE for now, we'll see how to proceed later.

-------------
Roberto Franceschetti

http://www.logsat.com" rel="nofollow - LogSat Software

http://www.logsat.com/sfi-spam-filter.asp" rel="nofollow - Spam Filter ISP


Posted By: __M__
Date Posted: 28 March 2007 at 6:41am

Just to add my 2 cents worth in, I have been following the whole SFE development since it's announcement. I am using the SFE RCs in a live environment to resolve the "mail splitting" issue. However due to current infrastructure (and time) I am yet to implement the "enterprise" features of SFE.

With that said I have for a while been contemplating the All Domains/Default scenerio which Web Guyz is mentioning. I too believe it would be best to have some sort of "inheritance".

I think a "server wide/default" set of rules (especially for keywords etc) should be a necessity.

Then the option of the current style defaults for not-customized domains or the alternative of customization for that domain.

Sorry if I didnt pipe up about this earlier, I think I sort of assumed that I had misunderstood the whole defaults thing and Web Guyz has now bought this out in the open.

With that said I think LogSat has done a great job with the development of SFE and attending to our bug reports etc, I do think that this "server wide defaults" thing needs to be addressed before many of us will choose to go live in enterprise mode.



Posted By: Desperado
Date Posted: 26 April 2007 at 11:08am
Hmmm ... I knida agree with everybody on some level.  I do feel that *some* lists that domains have may want the ability to sem-inherit a default list.  "Semi" meaning that if I make a change to the "Default" list, the inheritance should be only to add or remove the new settings to the domains that have inheritance BUT NOT remove entries the customer added or put back in entries that they removed.  This sounds VERY involved however.

-------------
The Desperado
Dan Seligmann.
Work: http://www.mags.net
Personal: http://www.desperado.com



Posted By: WebGuyz
Date Posted: 26 April 2007 at 1:22pm

Why not have both the system wide defaults and domain specific for each list like blacklist keywords,blacklist IP's, etc. When the text file is being built just read the specific default records and then the individual domain records for that specific table.

If a system wide default causes grief for a single domain just create a corresponding whitelist entry for that domain.

Some tables I think should have a 'default':

SURBL
MAPS
Blacklist Keywords
Blacklist FROM
Blacklist IP's
Blacklist Domains

 



-------------
http://www.webguyz.net



Print Page | Close Window