I've found as we become more agressive with keywords and rules we obviously start to generate more false-postive's for our clients.

So then our clients start asking how they can maintain a list of domains that are their "VIP" or top client domains so we don't block ANY emails from that domain EVER.

That's a tough question because I don't want to add the domain to the Excluded list in case another cllient wants that domain blocked.... so what do we do?

Here's an idea:

What if we could manually add line to the AutoWhiteList like:

*@VIP.com|*@clientdomain.com

Same concept as AutoWhiteList mapping two email address's but we WhiteList a domain to a domain so it's not going to affect other clients.

Going a step further we could give the Admin's the a button to "Allow Domain" and we wouldn't have to worry they open up or compromise the system by allowing a domain everyone else want's blocked. This would allow the domain only for that domain.

Let me know what you think,

Bob

Roberto,

We haven't heard from you? Is it possible to either add the wild card ability to the AutoWhiteList.txt file OR create a "DomainWhiteList.txt" that will allow us to allow an entire domain to an entire domain mapping.

Again what's happening is people keep logging in to forward emails to each individual person in their organization. If we/they could "Allow entire domain" ONLY to their domain this would be an awesome feature!

This would also overcome Dan's problem (which we have seen also) when there are minor changes in the sending email. We've seen this from ebay.com also.

Thanks in advance,

Bob

Roberto,

I just tested this and found that the wildcards in fact *do* seem to work in both the source and the destination or both so ... now I just need to clean up my auto-allow list and with luck, after a few days it will only need to be looked at once in a while.

Thanks!

Dan S.

Just did more testing and found that daseligmann@*|dan@*

allows daseligmann@anything.con >> dan@anything.com  so this, too is cool.  Check my work please!

das

Roberto,

This is AWESOME! and I agree I don't care if it's called a bug or not, it works!

Funny I had a thought to just test it but figured I'd better post before going off into left field! Next time I'll just try it! :-)

Ok now that we have that working let me explain "taking this a step further."

We have developed a custom web interface and I also believe the supplied web interface gives clients the ability to login and review quarantined messages. They then click a check box next to any quarantine message and click a button to forward the messages to them.

Our programmers say that Logsat does a periodic update and when it see the "Del" filed in the Quarantine DB change to a "1" it's added automatically to the "AutoWhiteList.txt" file.

So I'd like to add a button that say's "Allow Domain." In the past this scared everyone because you don't want a client allowing a domain that someone else wants blocked.

So IF you would add another field to the Quarantine DB like "Allow_domain" and IF on the updates if it saw this column with a "1" it would add "*@sending_domain.com|*@receiving_domain.com to the AutoWhiteList.txt file.

Now our clients can allow a domain without affecting anyone else!

Also to backup what Dan posted our AutoWhitelist would be very short and clean.

IF this is impossible another client asked for a way to "Manage a VIP list of domains" for their company. Instead of a "Allow Domain" button they could simply add domains to a list they don't want blocked. Again this would be a private list that would update the AutoWhiteList.txt file. Heck maybe we are talking about a AutoWhiteListDomain.txt file being added?? They could add domains and it would then add the entry to some type of AutoWhiteList.txt file.

Send me your feedback Roberto, our guys say they could program our site to do this but it would be much cleaner if you can add it to the Logsat program itself!

Let me know what you think, we'd be happy to do some testing!

Thanks,

Bob

Thanks for the reply. For now we will manually manage the AutoWhiteList.txt vs. programming our own solution. Again I'd prefer to manage this for now until an "official release" from SpamFilter.

Keep us updated!

Thanks,

Bob