RE: [Nms-cgi-devel] Questions regarding email filter...

[Simon W. <es...@ou...>]

On Wed, 2003-02-12 at 12:51, Wizard wrote:
> > I still think it is a requirement to block whole sub-domains, for
> > instance *@*.kr or *@*.spammers-r-us.com
> 
> I'm not sure that we differ on that, but there could be some problems with
> it either way: how does the second example treat the example given yesterday
> of info@dk? or fr...@sp...? Depending on how it parses, we could
> block neither or both. Is it better to fail conservatively, aggressively, or
> not at all? These are all things I'm trying to consider (my brain hurts).

We don't but your message seemed to say full string matches and didn't
cover these case.

I think the syntax for specifying these filters needs to be domain
specific and most definitely NOT regexes. It's too easy for users to get
these wrong. I would expect the code to turn the syntax into regexes.
Something like this maybe:

info@dk -> /^info@dk$/

*@dk -> /@dk$/

*@*.kr -> /\bkr$/ 

fred@*.spammers.com -> /^fred@.*\bspammers.com$/
 
In this case, you treat the period in the filter syntax as meaning word
boundary and munge into the regex accordingly.

S.