Re: [ietf-822] References: none

"John Levine" <johnl@taugh.com> Wed, 01 May 2019 02:14 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E59EE120088 for <ietf-822@ietfa.amsl.com>; Tue, 30 Apr 2019 19:14:27 -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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=5M46fe8p; dkim=pass (1536-bit key) header.d=taugh.com header.b=abD4icZQ
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 HljigeXVY3kB for <ietf-822@ietfa.amsl.com>; Tue, 30 Apr 2019 19:14:26 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 171AB120004 for <ietf-822@ietf.org>; Tue, 30 Apr 2019 19:14:25 -0700 (PDT)
Received: (qmail 90195 invoked from network); 1 May 2019 02:14:24 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=16051.5cc90100.k1904; i=johnl-iecc.com@submit.iecc.com; bh=OP+HktHKT1hHRLiHMAiggzjPM2VfmgQ6JTGfgXMh9ps=; b=5M46fe8pZyrhqsn84IL83Xu+jE2FG5NxIP007MZ9xXcrx0tffzyCul4ieb6aZkzjX1ZuRsxVe0IV3nG915zffXYAS9iroFAAbIZKVmRR5BP3SKDFTN0vyNFBZvuYoq0UnNlFieBGyrDpGeDtu0WNrHo5IT716fmYf446tv0AVijTizBsbx0SpJTQ9Jq8aKW59KNXds3jpM/9i1G2zOJZUOMuHITpMRwmcJlJ5j1wsuXytbdg16QMMhKc22dSdrFc
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=16051.5cc90100.k1904; olt=johnl-iecc.com@submit.iecc.com; bh=OP+HktHKT1hHRLiHMAiggzjPM2VfmgQ6JTGfgXMh9ps=; b=abD4icZQw9xSkM/vE0YWbCi0CrD6nMrmEOvy0/Z8vpuqn6sqBr9JxZIVPMmsaYL9XM8NhIEmBEVHFjR3gz2S9n3CJ4jUOtn4Sevbrqq+BZB+aiV9t6dVP2ar8ov6wwjc4YGfS9RaFFTIBoBpwgFW4qG1O/xpTggZtw3hYVkXkWeCOMp8kiPri31C2+H4bpEvYF7PdT6GZzhOiBTVqHcvKgG3xKOGkT3or/QvPdxLLMnCZMQlFUv8zo6BRTlkwC03
Received: from ary.qy ([64.246.232.221]) by imap.iecc.com ([64.57.183.75]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, johnl@iecc.com) via TCP; 01 May 2019 02:14:24 -0000
Received: by ary.qy (Postfix, from userid 501) id E55F0201328935; Tue, 30 Apr 2019 22:14:23 -0400 (EDT)
Date: 30 Apr 2019 22:14:23 -0400
Message-Id: <20190501021423.E55F0201328935@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: ietf-822@ietf.org
Cc: johngalton217@gmail.com
In-Reply-To: <CABHfyPSGFveB+_8UGUTFjuqab2-9UVKSJggGWinTxrwKijM-pw@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-822/DzbleHrE_5lRfES2rl2TwKKnAFw>
Subject: Re: [ietf-822] References: none
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" <ietf-822.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-822/>
List-Post: <mailto:ietf-822@ietf.org>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2019 02:14:28 -0000

In article <CABHfyPSGFveB+_8UGUTFjuqab2-9UVKSJggGWinTxrwKijM-pw@mail.gmail.com> you write:
>Is there any standard way for a mail client to tell recipient that "I'm
>aware of References and In-Reply-To headers but this email is not a reply
>or related to another email"?

The short answer is no.

It might be interesting to put the message's own message-id in the
references and reply-to header and see what happens.