Re: [exim] Feature Needed - Main_domain

Top Page
Delete this message
Reply to this message
Author: V. T. Mueller
Date:  
To: 'Exim-users'
Subject: Re: [exim] Feature Needed - Main_domain

Good morning,

Marc Perkel schrieb:
> Chris Meadors wrote:
>> Marc Perkel wrote:
>>> If the part second to the end is co com net org then it's 3 part.
>>> warn    message = X-Maindomain: \
>>> ${if 
>>> match{XX${extract{-2}{.}{${domain:$h_From:}}}XX}{XX(co|com|net|org)XX}\
>>> {${extract{-3}{.}{${domain:$h_From:}}}.${extract{-2}{.}{${domain:$h_From:}}}.${extract{-1}{.}{${domain:$h_From:}}}}\ 

>>>
>>> {${extract{-2}{.}{${domain:$h_From:}}}.${extract{-1}{.}{${domain:$h_From:}}}}\
>>>
>>> }
>> What about com.com? Which is CNet's domain.
>> Additionally, Japan uses .ne.jp and .or.jp. Not to mention Romania who
>> uses: .tm.ro, .nt.ro, .nom.ro, .info.ro, .rec.ro, .arts.ro, .firm.ro,
>> .store.ro and .www.ro in addition to the .com.ro and .org.ro. Which I'm
>> sure a few of will collide with "main domains" of dotcoms. On top of
>> that many other countries have their own different second-level domains
>> defined.
> You're making my point. This needs to be in Exim because it's far to
> complex to do with a Regex.


Begging your pardon but you obviously aren't reflecting what Chris
pointed you at: there is a -both in number and in content- variable
amount of information /outside/ exim. It's rather pointless *how*
you're going to deal with it. It boils down to: adapting to such
kind of 'outer references' is an admin's job. Not a job for the core
software used.

So if such a function would be of much use for you, there will most
probably no way except "ad aspera ad astra" - means you would have
to figure out how to use complex lsearch or a database query to
access the data you collected from iana.org and a neat number of
national registrars. Doable. But probably not worth the effort.


Regards,
vt