RE: [Nms-cgi-devel] Anyone...Anyone...?

[Wizard <wi...@ne...>]

> .co is not a valid tld, either generic or country code. See
> http://www.din.de/gremien/nas/nabd/iso3166ma/codlstp1/db_en.html
>
> .bl is not a tld in this example, uk is. It happens that the British
> Library for reasons dating back to antiquity, sit outside the generally
> accepted standard of .(co|ac|org).uk
>
> aol.police.uk is really going to mess you up :)
>
> I still believe that you cannot parse the ORGANISATION out of the domain
> part of the email address without more semantic information than you
> have available.

'Organization' - that's the work I was looking for! (note: Yanks use 'z')
I never thought that I would be able to filter every possible email without
at least a few failures. My only real goal was to offer the best possible
solution to the problem with the least amount of complexity for the user.

As far as '.bl', I'm still not sure what sort of situation we're talking
about. If it is some sort of generic domain like '.co' (standard or not)
then we can add it to the $valid_tlds variable. It apparently doesn't matter
if it conflicts or not, it will still work (.co is actually a ccTLD for
Columbia). However, it appears as though it is the actual organization name
though (www.bl.uk), in which case fr...@ao... shouldn't be filtered by
*@*.aol.*. What I am seeing in fr...@ao... is a machine name 'aol' within
the bl.uk organization. On the other hand, aol.co.uk is actually the mail
target for the aol.co.uk organization, where .co is a generic class id (or
whatever it should be called) similar to .org or .com as a gTLD.

> You cannot expect to have *.aol.* block just websites belonging to
> AOL/Time Warner.

I don't, but I do expect it to at least try to determine if it is an
organization name, cname, gTLD/ccTLD or other type of qualifier (like
.co|.ac). When a user enters *@aol.*, I am assuming that their target is the
organization 'aol', not a machine name. I think that the script should
assume that as well. Typically, I would suspect that most filter globs will
either target a particular user, an organization, or perhaps a country. That
is what the mechanism is designed to address. The system doesn't make the
machine name a first choice, but rather it's last choice. That is what I
would expect, and I have assumed that of the users of the script. I am not
saying that I'm not mistaken with this assumption. (I am very good at being
wrong ;-).

> You might work on something that allows *.aol.*.uk or *.aol.*.* to match
> in the third level domain.

Let me know what you get, but that's the problem I was struggling with. How
do you do that without filtering nearly anything that contains that value?
For instance:
FILTER:  *@news.*.*  ->  meaning 'fr...@ne...'
Email:   fr...@ne...
whereas with the present system, *@news.* will assume 'news' to be the
organization name and not the machine name and will pass 'fr...@ne...'
but deny 'fr...@ne...'

I just got your email, I'll take a look.
Grant M.