Spam Filter ISP Support Forum

  New Posts New Posts RSS Feed - Feature upgrade: Could we use wildcards in AutoWhiteList to allow doma
  FAQ FAQ  Forum Search   Register Register  Login Login

Feature upgrade: Could we use wildcards in AutoWhiteList to allow doma

 Post Reply Post Reply
Author
CyberBob View Drop Down
Groupie
Groupie


Joined: 26 January 2005
Status: Offline
Points: 43
Post Options Post Options   Thanks (0) Thanks(0)   Quote CyberBob Quote  Post ReplyReply Direct Link To This Post Topic: Feature upgrade: Could we use wildcards in AutoWhiteList to allow doma
    Posted: 13 January 2005 at 12:12pm

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

Back to Top
Desperado View Drop Down
Senior Member
Senior Member
Avatar

Joined: 27 January 2005
Location: United States
Status: Offline
Points: 1143
Post Options Post Options   Thanks (0) Thanks(0)   Quote Desperado Quote  Post ReplyReply Direct Link To This Post Posted: 16 January 2005 at 6:54pm

Bob,

I can not find the posting, but this was discussed before and LogSat had a reason that your requested syntax is not supported.

Having said that, I am going to be a minor thorn in Roberto's side and say that I agree with your request though not totally for the same reasons.  My issue is that the darn list servers change the "From" address every time they send so the added entry in the AutoWhiteList becomes rendered useless.  As an example, I have literally dozens of the following:

bounce-129562_html-369636920-706172@bounce.exacttarget.com|dclaeys@rksresearch.com
bounce-183712_html-640139427-701950@bounce.exacttarget.com|dclaeys@rksresearch.com

which I have to routinely remove because the list gets filled up with these useless FROM|TO pairs.

Oh well.

Regards,

Back to Top
CyberBob View Drop Down
Groupie
Groupie


Joined: 26 January 2005
Status: Offline
Points: 43
Post Options Post Options   Thanks (0) Thanks(0)   Quote CyberBob Quote  Post ReplyReply Direct Link To This Post Posted: 20 January 2005 at 1:30pm

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

Back to Top
LogSat View Drop Down
Admin Group
Admin Group
Avatar

Joined: 25 January 2005
Location: United States
Status: Offline
Points: 4065
Post Options Post Options   Thanks (0) Thanks(0)   Quote LogSat Quote  Post ReplyReply Direct Link To This Post Posted: 21 January 2005 at 12:10am
Bob,

As Dan mentioned, in a previous posting we provided an explanation as to why that was not possible (we did not allow wildcards in that list for better performance).

However we've been re-examining the scenario, and I believe I was wrong in that post. It is late at night and I may be not be thinking 100%, but it does seem that your idea is indeed supported in the latest pre-release build 402. I've tried the syntax:

*@VIP.com|*@clientdomain.com

and it had the desired effect.

We'll need more testing as this was not really the intended behavior, but hey, if it works it's just what you wanted, and we'll make it a supported configuration.

I'm not sure I understood the last part of your post "Going a step further". Can you please expand on that?

Roberto F. LogSat Software

Roberto F. LogSat Software
Back to Top
Desperado View Drop Down
Senior Member
Senior Member
Avatar

Joined: 27 January 2005
Location: United States
Status: Offline
Points: 1143
Post Options Post Options   Thanks (0) Thanks(0)   Quote Desperado Quote  Post ReplyReply Direct Link To This Post Posted: 21 January 2005 at 1:40am

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

Back to Top
LogSat View Drop Down
Admin Group
Admin Group
Avatar

Joined: 25 January 2005
Location: United States
Status: Offline
Points: 4065
Post Options Post Options   Thanks (0) Thanks(0)   Quote LogSat Quote  Post ReplyReply Direct Link To This Post Posted: 21 January 2005 at 11:02pm
...Well, I don't know what to say here. By design, we did not intend the wildcards to work to make processing faster. Obviously we found a bug in the code that still allows them.

I believe this is the first time I ever found a bug in a program that users (and developers) are happy to have.

This will be catalogued as a BUG, and I publicly declare that it won't be fixed...

:-)

Roberto F. LogSat Software
Back to Top
CyberBob View Drop Down
Groupie
Groupie


Joined: 26 January 2005
Status: Offline
Points: 43
Post Options Post Options   Thanks (0) Thanks(0)   Quote CyberBob Quote  Post ReplyReply Direct Link To This Post Posted: 24 January 2005 at 12:26pm

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

Back to Top
LogSat View Drop Down
Admin Group
Admin Group
Avatar

Joined: 25 January 2005
Location: United States
Status: Offline
Points: 4065
Post Options Post Options   Thanks (0) Thanks(0)   Quote LogSat Quote  Post ReplyReply Direct Link To This Post Posted: 24 January 2005 at 11:45pm
Bob,

Now that the "door has been opened" with the Autowhitelist thanks to our mistake :) more opportunities will become available. You have a very good idea, and the only thing that is slowwing us down to implement it is that we thread very carefully whenever a database schema change is involved. This requires that SpamFilter auto-updates the database table to add the new field, and we've always tried to do this without needing user intervention. However this may always not work properly...

I've added the request to the wish list. Your programmers are correct in all their assumptions, we'll see what we can do in making it more elegant in having SpamFilter take care of that.

Roberto F. LogSat Software
Back to Top
CyberBob View Drop Down
Groupie
Groupie


Joined: 26 January 2005
Status: Offline
Points: 43
Post Options Post Options   Thanks (0) Thanks(0)   Quote CyberBob Quote  Post ReplyReply Direct Link To This Post Posted: 25 January 2005 at 10:26am

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

Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down



This page was generated in 0.078 seconds.