Re: [art] whois email

Ned Freed <ned.freed@mrochek.com> Sat, 28 July 2018 15:04 UTC

Return-Path: <ned.freed@mrochek.com>
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 D2847130F04 for <art@ietfa.amsl.com>; Sat, 28 Jul 2018 08:04:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mrochek.com
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 2GC8glx9M-CX for <art@ietfa.amsl.com>; Sat, 28 Jul 2018 08:04:33 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (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 2BD5C130DC8 for <art@ietf.org>; Sat, 28 Jul 2018 08:04:33 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QVECC55SPC000E6U@mauve.mrochek.com> for art@ietf.org; Sat, 28 Jul 2018 07:59:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=201712; t=1532789968; bh=52BC0TFy2839Qv/qzUH3Mq1R7sZnOI6d/aCeC5ovFB8=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=E1aOtiK8B5SNoIsZu8AcNRO4URD/sTkxJ72Zjm6+0juCKnLYyB2m2T8hJdzbvjyvn V4oElh0uBCgvRaYWx4f13moPxqxff5swz7QQa57t3xN2WH/VP9BWtMBzEp5NXAZFcq 5PjCqRpV7fOsZDXiqCj14dKYPrqfB9xessFUGPgM=
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: TEXT/PLAIN; CHARSET="us-ascii"; format="flowed"; DelSp="Yes"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QVCMG8WF680002TJ@mauve.mrochek.com>; Sat, 28 Jul 2018 07:59:24 -0700 (PDT)
Cc: Ned Freed <ned.freed@mrochek.com>, art@ietf.org, hernani.marques@pep.foundation
Message-id: <01QVECC3EM5G0002TJ@mauve.mrochek.com>
Date: Sat, 28 Jul 2018 07:55:16 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Fri, 27 Jul 2018 22:13:59 -0600" <20180727221359.Horde.vDea-BzaaJR7kb9xOsou32v@box439.bluehost.com>
References: <20180726230438.Horde.Xg504r7eG3dtrafRNVk_0BF@box439.bluehost.com> <01QVCMU3B82S0002TJ@mauve.mrochek.com> <20180727221359.Horde.vDea-BzaaJR7kb9xOsou32v@box439.bluehost.com>
To: pradeep@explodingmoon.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/y09BqkzwbQveZQE1WsnR5tidjH8>
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 15:04:35 -0000

And with this you enter FUSSP territory:

  https://www.rhyolite.com/anti-spam/you-might-be.html

My assessement stands: Your proposal is completely unworkable.

And with that I'm done.

				Ned

> 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