If you're going to engage with RH, leave me out of it.
On 2023-05-01 at 11:14:12 UTC-0400 (Mon, 1 May 2023 09:14:12 -0600)
Philip Prindeville <philipp_s...@redfish-solutions.com>
is rumored to have said:
On May 1, 2023, at 3:48 AM, Reindl Harald <h.rei...@thelounge.net>
wrote:
Am 30.04.23 um 20:54 schrieb Philip Prindeville:
On Apr 28, 2023, at 12:17 PM, Philip Prindeville
<philipp_s...@redfish-solutions.com> wrote:
On Apr 28, 2023, at 10:24 AM, Reindl Harald
<h.rei...@thelounge.net> wrote:
Am 28.04.23 um 18:11 schrieb Philip Prindeville:
On Apr 25, 2023, at 6:28 AM, Bill Cole
<sausers-20150...@billmail.scconsult.com> wrote:
On 2023-04-24 at 16:32:55 UTC-0400 (Mon, 24 Apr 2023 14:32:55
-0600)
Philip Prindeville <philipp_s...@redfish-solutions.com>
is rumored to have said:
I thought the matching included subdomains, and seem to
remember that working.
It never has. At least not in the past 17 years.
Then how do pools of servers like
*.protection.outbound.outlook.com get handled?
as * is always handeled at globbing
*.example.com
*@example.com
Maybe I'm missing something, but the code brackets ${domain} with
\Q and \E so globbing wouldn't work.
if ($rdns =~ /(?:^|\.)\Q${domain}\E$/i) { $match=1; last }
But it *is* anchored on the left hand side by either beginning of
line *or* dot
and what do you think "*" will do with the anchoring?
^*
And that will continue to glob inside \Q ... \E ?
-Philip
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
