Hello,
This is at least the 2nd time in recent times that we got this
behaviour below.
I am now reporting the last one that happened this night, however
similar one happened some months ago aswell.
I believe something is miscoded at RIPE side, but here it goes:
Yesterday, Sun, 2 May 2021 22:44:17 +0000 (UTC), i got an email from
RIPE, via "zendesk" saying:
######################################################################
Subject: #371145 - Action Required: Confirm Abuse Contact
Information (RIPE NCC)
...
We have sent a validation link to this abuse contact. Please click on
this link to confirm that the email address is valid and close this
ticket.
######################################################################
Headers from email received from zendesk: (sent at 22:44:10 UTC)
######################################################################
Received: from x ([x])
by x (mail.x [x]) (amavisd-new, port x)
with ESMTP id kNt8Ea9EyGXA for <x>;
Sun, 2 May 2021 22:44:17 +0000 (UTC)
Received: from outbyoip8.pod18.euc1.zdsys.com
(outbyoip8.pod18.euc1.zdsys.com [188.172.138.8])
by x (Postfix) with ESMTPS id 4FYLkn3w7Yz2NlCH
for <x>; Sun, 2 May 2021 22:44:17 +0000 (UTC)
Received: from zendesk.com (unknown [10.218.219.234])
by outbyoip8.pod18.euc1.zdsys.com (Postfix) with ESMTP id
4FYLkf5rcyz14K2j;
Sun, 2 May 2021 22:44:10 +0000 (UTC)
Date: Sun, 02 May 2021 22:44:10 +0000 (02/05/2021 23:44:10)
From: RIPE NCC Support <supp...@ripe.net>
Reply-To: RIPE NCC Support <supp...@ripe.net>
Cc: Nuno Vieira <x>, Member Contact <x>
Message-Id: <
do8qlg3d2p_608f2b3a67286_2b2aeb05f3b964287882c_sp...@zendesk.com>
In-Reply-To: <do8qlg3...@zendesk.com>
Subject: #371145 - Action Required: Confirm Abuse Contact Information
(RIPE NCC)
######################################################################
Headers from RIPE with the magic link: (sent at 22:48:22 UTC)
######################################################################
Received: from x ([x])
by x (x [x]) (amavisd-new, port 10024)
with ESMTP id 5Em8E0bGU80N for <x>;
Sun, 2 May 2021 22:48:32 +0000 (UTC)
Received: from pikapika.ripe.net (pikapika.ripe.net
[IPv6:2001:67c:2e8:11::c100:1315])
by x (Postfix) with ESMTPS id 4FYLqh5LRtz2NlCH
for <x>; Sun, 2 May 2021 22:48:32 +0000 (UTC)
Received: from [193.0.1.40] (helo=limousin.ripe.net)
by pikapika.ripe.net with esmtp (Exim 4.94)
(envelope-from <unr...@ripe.net>)
id 1ldKsw-00010y-CN
for x; Mon, 03 May 2021 00:48:22 +0200
Date: Mon, 3 May 2021 00:48:22 +0200 (CEST) (02/05/2021 23:48:22)
From: RIPE Database Administration <unr...@ripe.net>
To: x
Message-Id: <1840504553.488.1619995702...@limousin.ripe.net>
Subject: Action Required: Confirm Abuse Contact Information (RIPE NCC)
######################################################################
Context:
The allegated confirmation email with a link is only beign sent after
the other contact to the LIR has been made, and those allegations are
false. I have double checked mail server logs and there is no error,
connection attempt or whatsoever that can support the "There was a
transient network fault on the path to the mail server".
######################################################################
"The email address in the "abuse-mailbox:" attribute for the abuse-c
ROLE object x-RIPE failed the automatic validation test: x
There was a transient network fault on the path to the mail server.
We have sent a validation link to this abuse contact. Please click on
this link to confirm that the email address is valid and close this
ticket."
######################################################################
My Questions are simple:
- Did anyone else got this very same behaviour/situation ?
- I would like to understand the rationale behind this, and if this is
a bug or a feature...
--
Kind regards,
Nuno Vieira
edgoo networks
datacentre and it services
