For the tblwl_autowhitelistforcedelivery table add a field called date and create a ini setting called expireautowhitelistentry=x where is x is settable.

This way IF a date was entered in the date field and IF it was older then then the expireautowhitelistentry=x entry it would be deleted.

I know a few users currently do something like that in SFI db to keep the autowhitelist from getting stale. We have a couple of pay day stores and they do business with a lot of users, but only once, so they might get tons of entries, but if we could expire stale addresses then it might help keep the list size manageable.

Another wish would be some sql scripts to automate copying over default domain stuff to ALL our domains. Easy to do manually if you have just a few domains but it can take a while if  you have hundreds to do. Also, SFE seems to be unresponsive while its copying all the info into the tables especially if you have hundreds of keywords entered over a long time. Would be better to do it offline of SFE via script.

Lookin good! 

I believe the unresponsive issue was a result of telling SFE to not use defaults of ALL DOMAINS and doing a copy files from ALL DOMAINS. The darn autowhitelistdelivery table has over 34000 entires and of course it created 34000 more for the domain I was working with, this on a shared MS SQL server during the middle of the day with my production SFI's hammering away. So its not SFE's issue, but rather planning on my part. I realize I need to zero out the autowhitelistdelivery file and then write a script to go through line by line and add it with the correct domainid so that there is a total of 34000 lines only and whatever gets added in the future.

Your right about adding the date field and creating a script to delete. After I wrote this post I realized that it was something I could easily do and should not have have been requested.

Expect more floundering around as I get more familiar with SFE, but starting to see the potential and having everything SQL based makes automation easy.