Re: [art] whois email

pradeep@explodingmoon.org Sat, 28 July 2018 04:22 UTC

Return-Path: <pradeep@explodingmoon.org>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6652D130E54 for <art@ietfa.amsl.com>; Fri, 27 Jul 2018 21:22:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.837
X-Spam-Level:
X-Spam-Status: No, score=-0.837 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_NUMERIC_HELO=1.164, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=explodingmoon.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f25Iob-PmQEF for <art@ietfa.amsl.com>; Fri, 27 Jul 2018 21:22:02 -0700 (PDT)
Received: from gproxy3-pub.mail.unifiedlayer.com (gproxy3-pub.mail.unifiedlayer.com [69.89.30.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E455F130E50 for <art@ietf.org>; Fri, 27 Jul 2018 21:22:01 -0700 (PDT)
Received: from cmgw15.unifiedlayer.com (unknown [10.9.0.15]) by gproxy3.mail.unifiedlayer.com (Postfix) with ESMTP id 04E3F41429 for <art@ietf.org>; Fri, 27 Jul 2018 22:14:00 -0600 (MDT)
Received: from box439.bluehost.com ([69.89.31.239]) by cmsmtp with ESMTP id jGcBfM017j0sojGcBfJnWU; Fri, 27 Jul 2018 22:13:59 -0600
X-Authority-Reason: nr=8
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=explodingmoon.org; s=default; h=MIME-Version:Content-Type:In-Reply-To: References:Subject:Cc:To:From:Message-ID:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=aG8v4LlsoScdcsOJ8OxQvvYNzRRicbqEG9AxdXt3JiY=; b=CLrwNfQpO0uUe/dq/+fsUeXPm tvBYxucj4xQODk/TBCjbNE15SEgMoWWhsRrE2Qz3nlop2/FRfBjNMTQCMq/h6jUDn+LwEUidx05zX qJEmXrhdaELprEp9pE31EoRIj+OMvGSkWmT7/QySXRu+XbLjPRX7Sks0IhbwhPb6PUtYI5e+Sw44M 3CXBU4ac/SIpe0Io+5Kk4zwd+rAbcxBsUqESsUqChUzjBWTAirtJySWMpVZCMeaq+DXzs2aiwbX+x LNwdJAbVGI5O7POhEX3TvY1mljuLXxY+FNXswfL8C9VFgjzl/38cF0J0wanpNlLQBEX5kytPBYf1D aUZwVfWfA==;
Received: from [127.0.0.1] (port=11071 helo=box439.bluehost.com) by box439.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <pradeep@explodingmoon.org>) id 1fjGcB-000YXm-Hl; Fri, 27 Jul 2018 22:13:59 -0600
Received: from 112.133.229.97 ([112.133.229.97]) by box439.bluehost.com (Horde Framework) with HTTPS; Fri, 27 Jul 2018 22:13:59 -0600
Date: Fri, 27 Jul 2018 22:13:59 -0600
Message-ID: <20180727221359.Horde.vDea-BzaaJR7kb9xOsou32v@box439.bluehost.com>
From: pradeep@explodingmoon.org
To: Ned Freed <ned.freed@mrochek.com>
Cc: art@ietf.org, hernani.marques@pep.foundation
References: <20180726230438.Horde.Xg504r7eG3dtrafRNVk_0BF@box439.bluehost.com> <01QVCMU3B82S0002TJ@mauve.mrochek.com>
In-Reply-To: <01QVCMU3B82S0002TJ@mauve.mrochek.com>
User-Agent: Horde Application Framework 5
Content-Type: text/plain; charset="utf-8"; format="flowed"; DelSp="Yes"
MIME-Version: 1.0
Content-Disposition: inline
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box439.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - explodingmoon.org
X-BWhitelist: no
X-Source-IP: 127.0.0.1
X-Source-L: Yes
X-Exim-ID: 1fjGcB-000YXm-Hl
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: (box439.bluehost.com) [127.0.0.1]:11071
X-Source-Auth: pradeep@explodingmoon.org
X-Email-Count: 2
X-Source-Cap: ZXhwbG9kaTQ7ZXhwbG9kaTQ7Ym94NDM5LmJsdWVob3N0LmNvbQ==
X-Org: HG=bhcustomer;ORG=bluehost;
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/gh3lTr4pshiO-6pMkvlkExe5fgo>
Subject: Re: [art] whois email
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Jul 2018 04:22:04 -0000

Quoting Ned Freed <ned.freed@mrochek.com>:

>> On 26.07.2018 17:18, Ned Freed wrote:
>
>>> And all this was back when privacy concerns were, if anything, an
>>> afterthought.
>>> These days the potential liability created by new laws make this idea
>>> completely impractical.
>>>
>>> tl;dr: This is a nonstarter.
>
>> Especially considering that after GDPR went into effect lots of
>> registries (e.g., in the US) went over to mask whois data; it would also
>> create additional spam problems with data harvesting.
>
>> How do you control SPAM then?. How do you say an email is authorised
>> or a spammer in a registry that can be queried by the email
>> software/protocols. Spammers can get emails from not only WWW but
>> ISP's and social media like facebook twitter also.whois of email can
>> have only one public field authorised or unauthorised.
>
> This is neither the time nor the place to provide you with a tutorial
> on the basics of spam control. Suffice it to say it's being done without
> the benefit of your proposal.
>
> 				Ned
No, i give you a simple solution to SPAM control. To have an whois email
standard and a field that can be queried authorised/unauthorised in the email
software. You talk like only engineers, not email users.
I dont need your tutorial, i need a solution. My life is in danger because of
email spammers. I proposed a solution in the draft. I need to say in my email
only emails from authorised should be recieved. A spammer is a  
spammer, it cannot
be determined by the content of the email, but by his/her past actions/emails.
In addition i should be able to say i want to only hear from those who  
have a phone number and those who can disclose their phone numbers.A  
email registry standard is necessary.
Pradeep Kumar Xplorer