IETF Logo Mail Archive

Re: [ietf-smtp] Proper definition of the term "email payload".

Viruthagiri Thirumavalavan <giri@dombox.org> Sun, 31 March 2019 18:32 UTC

Return-Path: <giri@dombox.org>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55399120026 for <ietf-smtp@ietfa.amsl.com>; Sun, 31 Mar 2019 11:32:31 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dombox.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 Qo3otN6ykLAd for <ietf-smtp@ietfa.amsl.com>; Sun, 31 Mar 2019 11:32:29 -0700 (PDT)
Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE86C120021 for <ietf-smtp@ietf.org>; Sun, 31 Mar 2019 11:32:29 -0700 (PDT)
Received: by mail-yb1-xb31.google.com with SMTP id c2so2714002ybn.1 for <ietf-smtp@ietf.org>; Sun, 31 Mar 2019 11:32:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dombox.org; s=default; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=A/Gi18GT/Gt2E+c+j/4raM+Dlokf/LLnnqy6zM3jfhY=; b=QPoLw/Q6AUDhXR+ReQDXuRVIPGM1LQg3SeAylXaSBlv0LIGZZyJ/OFzODBp33YwgWh 9Dda9SW5E8A7sdt1uGd9zPA6PVjnj/l1MmOBtkRFG2t1hKue4cl7pnbWiSAsCQfx86LC R5f0dF7iP06WEWRWAnqMqfKgZ53Fc+gIJL62h5rmzuhcGCvjDMZCLZAV/sQxGuixBDwV sgXcbGPV4w79bf5TaYxcB9+RzRXdr5t/NimZYBZ/pk4WZAweFnDNethlidTQKH2+PRBy 6b6tPKZZC+th+0x2goJ2KuI4ukzLXCLJtKuxLCd8TwSEOO3FEt8d+7e+uuWHFo0cB7wA loLA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=A/Gi18GT/Gt2E+c+j/4raM+Dlokf/LLnnqy6zM3jfhY=; b=qOjLC+uRh/Z7mPJS7PljuKFI9QSIacYGy9boQy9GgiPV0Fq/E1DOQbP6TzEGfoIfJE w5TYf10MKD9UMTciLPHPSAfCEIwSaJgrtJfDoTwnZrb4NZ6A5rUwsfpzhtnRIlR6LHuN TT8YmTjSABge6YVAv+bu84Ec8YSj8AZD6lrdYjxbbsbx7XEEfV9/uu1zkm3ERa86Dhys fwHbUVDoNF3xStps1lMolii37oJ8Mh07OqnHEarFCYNUb+PGTQUCe4pF0FfL4GiCVMOu 0TnFUKEQXqL2fmm1jrAhZw9H39mLrMkYF4N6rwVwU3GT7fWsJvvIyoXn38bWQ96PtsY1 ljwg==
X-Gm-Message-State: APjAAAXFb8TvIRifotan2j4PnRCrtmDzW9+XCU82WNrdtxpM9FOzPuFz wxfyI9Z0ipQ1yPwmiCmTU22zZhIq9a06MWJYfc1/iA==
X-Google-Smtp-Source: APXvYqwAMV08YC56LcxbG2TQHo/nD6F9ZNa2O+frDSyIvWijaPlim2qKJhC7x0bO5lYlNl7VK930W7Z6wIeeSziZJ88=
X-Received: by 2002:a25:217:: with SMTP id 23mr5959517ybc.298.1554057148936; Sun, 31 Mar 2019 11:32:28 -0700 (PDT)
MIME-Version: 1.0
References: <CAOEezJRM8ZVaWK6rtvP4ZH9CbN-itVof9_Zi8hf+wVym0cAxzA@mail.gmail.com> <cfbc2ac9-3599-b71b-7d35-7765db7ac81a@network-heretics.com> <CAOEezJQn4g4m4J+J-AdkjnR-uwusLDgcj+9MQjv4hNFZjaz0Zg@mail.gmail.com> <89dff1da-64d9-5641-46b7-91e8ad98087d@network-heretics.com>
In-Reply-To: <89dff1da-64d9-5641-46b7-91e8ad98087d@network-heretics.com>
From: Viruthagiri Thirumavalavan <giri@dombox.org>
Date: Mon, 01 Apr 2019 00:02:17 +0530
Message-ID: <CAOEezJT1+meBDE9SVd=dQgmUx+Wduh_q7HSdU1dMcE-CfMmbYA@mail.gmail.com>
To: Keith Moore <moore@network-heretics.com>
Cc: ietf-smtp@ietf.org
Content-Type: multipart/alternative; boundary="00000000000052cb2a058568204a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/M3RM-mlaGdrfSVlc0Qr-E5stNfc>
Subject: Re: [ietf-smtp] Proper definition of the term "email payload".
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Mar 2019 18:32:31 -0000

Ok, thanks for the clarification.

On Mon, Apr 1, 2019, 12:00 AM Keith Moore <moore@network-heretics.com>
wrote:

> On 3/31/19 2:25 PM, Viruthagiri Thirumavalavan wrote:
>
> > Thanks Mr. Moore for the input.
> >
> > The well known Python software already using that term. I don't want
> > others like me to follow the wrong terminology.
> >
> > If I'm wrong that's fine. But If I'm right, we should find a way to
> > define the term properly. e.g. Editing that wikipedia article.
> >
> > Thanks
>
> Somebody can edit the Wikipedia article if they want.   But we in IETF
> don't have the power to make everyone use terms consistently.  It's hard
> enough to get people to read our protocol specifications and implement
> them correctly.
>
> Ketih
>
> p.s. I still remember being part of a crowd insisting that the term
> "hacker" referred only to a particular style of working and implied no
> malice at all.  But the media insisted on using the term "hacker" to
> mean "someone who tries to break into someone else's computers" and they
> effectively changed the meaning of the term.
>
>
>

v2.23.0 | Report a Bug | By Email