Re: [art] whois email
worley@ariadne.com (Dale R. Worley) Mon, 30 July 2018 00:58 UTC
Return-Path: <worley@alum.mit.edu>
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 C049D130EBC for <art@ietfa.amsl.com>; Sun, 29 Jul 2018 17:58:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.092
X-Spam-Level:
X-Spam-Status: No, score=-0.092 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 Zzldo2H35j9K for <art@ietfa.amsl.com>; Sun, 29 Jul 2018 17:58:26 -0700 (PDT)
Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) (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 65C8B130DEA for <art@ietf.org>; Sun, 29 Jul 2018 17:58:26 -0700 (PDT)
Received: from resomta-ch2-05v.sys.comcast.net ([69.252.207.101]) by resqmta-ch2-11v.sys.comcast.net with ESMTP id jw3hf9SXVV6ASjwW1fja6H; Mon, 30 Jul 2018 00:58:25 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-05v.sys.comcast.net with ESMTPA id jwVzfMSLCtDLzjwW0fDlYD; Mon, 30 Jul 2018 00:58:24 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id w6U0wN9C007128; Sun, 29 Jul 2018 20:58:23 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id w6TLVUnx002899; Sun, 29 Jul 2018 17:31:30 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: pradeep@explodingmoon.org
Cc: art@ietf.org
In-Reply-To: <20180726230438.Horde.Xg504r7eG3dtrafRNVk_0BF@box439.bluehost.com> (pradeep@explodingmoon.org)
Sender: worley@ariadne.com
Date: Sun, 29 Jul 2018 17:31:30 -0400
Message-ID: <87r2jlohjh.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfCW7IzU05U0+T6ljYh0dI9U+CthxRTSHpPaHGosa/ycxjdGR1au68cuWWRKJtQAkLG0+Av7ZBSzIgYje2t/bqNygwX+eqmcn80r0FmsCouNKXCGKqnWp iJCJbhICuBZsuYpDLK1tlq50mzzZDUl4DiNP12Ci2YO4MrZ4jAuAiq3AIpF8jynL0YepygP+/3fIM17JcPlDjLWgMCGWCrI80oaavuwAsxpw4Vf45uvgBTG3 C/4bjs5759ladfAyoalvPVo1chbY6obcHGa5365W3zs=
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/LdI6gbvYjT4XrnY1XPjN-LKv2GU>
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: Mon, 30 Jul 2018 00:58:28 -0000
pradeep@explodingmoon.org writes: > 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. Certainly, I'm no expert here, but various difficulties are obvious. For instance, you don't really need a pure registry, because you could use an alternative mechanism that is exactly as secure: the sender could incorporate into the e-mail headers whatever information the registry is to carry. And you can see the latter proposal adds no security. The problem is that the registry has to somehow certify something about the center, rather than just being a place than any person can put arbitrary data. (The obvious choices are that the sender is known to behave well, or that the sender has a particular legal identity.) And also the receiver has to be able to verify that the message was actually sent by the claimed sender (who you would look up in the registry). Basically this is the "public key infrastructure" problem. A quick check says that there are 41 RFCs with "PKI" in their titles. So a great deal of work has been done on that, and I don't think anyone thinks it has been satisfactorily solved. Then again, the problem of trust in non-online life has not been solved either. Dale
- [art] whois email pradeep
- Re: [art] whois email Ned Freed
- Re: [art] whois email pradeep
- Re: [art] whois email Ned Freed
- Re: [art] whois email Stephane Bortzmeyer
- Re: [art] whois email Dale R. Worley
- Re: [art] whois email Stephane Bortzmeyer