On Fri 24/Sep/2021 19:55:51 +0200 Slavko Via Mailop wrote:
Dňa Fri, 24 Sep 2021 12:36:23 -0400 Bill Cole via mailop <[email protected]>
napísal:
On 2021-09-24 at 11:50:24 UTC-0400 (Fri, 24 Sep 2021 17:50:24 +0200) Slavko via
mailop <[email protected]> is rumored to have said:
While i cannot comment mentioned OVH domain, i will ask, why
anyone have to know from WHOIS of my domain my name, or my
address or anything about me as private person? Yes, if someone
has archive of WHOIS response, it was there and i was not happy
from that. Are you having label with these info at top of face
when you are walking on the street?>>
Bad analogy.
Good analogy, as street is as public as the Internet is. You do not
answer if are you publishing your identity on the street.
Yes, you have to publish your identity if you open a shop or even a stall on
the street.
Owning an operational domain name makes you a public person. A domain
name is a claim on a specific piece of the public commons of the DNS.
In many places (including the US and at least some European
countries) you can only own land if your 'title' to that land is
registered with the government in an open public record. In the US,
that title includes the record of past ownership and even sales
prices. A domain name is intrinsically connected to public
interaction.
And that is what GDPR exactly prevents. That anyone want/require that
others have to publish, what they don't want, only because they want to
know it. The RFC defines ways how to contact domain's services
maintainers (postmaster, hostmaster, abuse, etc). What more you need to
know?
Do you mean RFC 2142? It is *not* an effective means to contact a domain's noc.
When you look at RFC, you will found, that it say about server's
identity (HELO/EHLO) nothing more, nothing less. And even tells, that
no one have to reject emails based on that identity checks...
That was never meant to depreciate the HELO/EHLO identity. That oversight is
removed in the next version of SMTP:
https://datatracker.ietf.org/doc/html/draft-ietf-emailcore-rfc5321bis
Instead, an accompanying applicability statement is going to say:
If the "Domain" argument to the EHLO command does not have an address
record in the DNS that matches the IP address of the client, the SMTP
server may refuse any mail from the client as part of established
anti-abuse practice. Operational experience has demonstrated that
the lack of a matching address record for the the domain name
argument is at best an indication of a poorly-configured MTA, and at
worst that of an abusive host.
https://datatracker.ietf.org/doc/html/draft-ietf-emailcore-as#section-2.1
I do not know how in USA, but in our country the government has tools
to know my identity, if there is legal reason (and court approve it).
How legal is your reason, beside that you want to know it?
The usual way is to go through the ISP, not the government. Not all ISPs hand
out an email address whereby to contact a responsive abuse team. It is common
practice to deny access to IPs corresponding to non-compliant providers.
Best
Ale
--
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop
