IETF Logo Mail Archive

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

Viruthagiri Thirumavalavan <giri@dombox.org> Mon, 01 April 2019 00:47 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 B50951201BE for <ietf-smtp@ietfa.amsl.com>; Sun, 31 Mar 2019 17:47:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, URIBL_BLOCKED=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 1WboCa3E42wV for <ietf-smtp@ietfa.amsl.com>; Sun, 31 Mar 2019 17:47:27 -0700 (PDT)
Received: from mail-yw1-xc2a.google.com (mail-yw1-xc2a.google.com [IPv6:2607:f8b0:4864:20::c2a]) (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 A14D912006F for <ietf-smtp@ietf.org>; Sun, 31 Mar 2019 17:47:27 -0700 (PDT)
Received: by mail-yw1-xc2a.google.com with SMTP id m207so2667357ywd.5 for <ietf-smtp@ietf.org>; Sun, 31 Mar 2019 17:47:27 -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=JRYGgI1NNZasVytocCM7PPdQ9GXbaHSHLL123xlIxyM=; b=Ewh3bQ+SfyCpdLdvbbHUEKaAiTd/vHXjhAMq3sbBgaSKD1tRJQuLEN9YLVEP7qEyLi SNG/FDmzJomnkm5jeV4iE/WqoHmV5JGvPmVjeXiwyePVujg1NF0lWuCq/dHOYUPAC3B6 VNVgawugCud67DkrDC5Hx0cB/XjyzFT+a+8RPXCP+3swRdYQz3IdhsodwSqHXQIC22dw ZBEiaOw2zX2vm72ls/EDabzSLWiUTVjTvYQLN37dLkZ4UPC1+yxFlBVFQ5bc9xxvfyg7 YY5hpIQ27tKJoYD1CNTgzVY7ehC1c7znJfAWJrL4oo8w51spwzJtvk5EnXIOo5gSQ5cK cBdw==
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=JRYGgI1NNZasVytocCM7PPdQ9GXbaHSHLL123xlIxyM=; b=aQO2KRcpeklrt5Utws1zeA4KY89axfXlULZ5vI3gJ92ShBGTBt3ex8FSDDFy7u6yEx tRxRFAIndS3Q7zxtjPEAI9wR+p7Nx4/Jfk/2bU9BCw380QUGhCBiy/LLCxOaItXpQhgX HP8D2y4s+x05aywYvjUsXlREyjVGoI3ZJ6FJQHrETFlmzB++OTqYgN/W77NQ65H2qmM0 xZ/O0u6uQryi8BxTh2hnx9QTkvaXfIgt9OXeELD/ZZLMek36HS2CBMYs05BpWg+gqPZ5 YnarVFSAwgVQnOt72e55nLjGUdVCgwYOaCnP1kmYq1JfT3W4eyt12cFnSyi4lx04XTen oanQ==
X-Gm-Message-State: APjAAAXNrwkefiUzwHvovcbAWEAydkSPyEJj8aJiXNG0PD1+ZRX1nkXS L25KtwX0yoqdV7FgmCywSjU7YPDW/PzRnqSEJPNPJQ==
X-Google-Smtp-Source: APXvYqzyRw4KSt+lCsHZpOQlCLjKH2cuOlS0IUvz86DR2b/kk7+EMxott5J528aSiwWzs4VEETkO5vM4/zPHRTkNZwo=
X-Received: by 2002:a81:a38b:: with SMTP id a133mr49694434ywh.423.1554079646871; Sun, 31 Mar 2019 17:47:26 -0700 (PDT)
MIME-Version: 1.0
References: <CAOEezJRM8ZVaWK6rtvP4ZH9CbN-itVof9_Zi8hf+wVym0cAxzA@mail.gmail.com> <d54267b1-b26d-6529-df5c-9f6d3477d374@gmail.com>
In-Reply-To: <d54267b1-b26d-6529-df5c-9f6d3477d374@gmail.com>
From: Viruthagiri Thirumavalavan <giri@dombox.org>
Date: Mon, 01 Apr 2019 06:17:15 +0530
Message-ID: <CAOEezJRimDb54WGV1+vE5X3RhoB1ss9jm0UG6-oh=LSTnGSVCA@mail.gmail.com>
To: Dave Crocker <dcrocker@gmail.com>
Cc: ietf-smtp@ietf.org, Barry Warsaw <barry@python.org>
Content-Type: multipart/alternative; boundary="0000000000004e044b05856d5dcc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/K7Bev04ysiUhRPTUjxGsq5XU67Y>
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: Mon, 01 Apr 2019 00:47:30 -0000

Thanks for the clarification.

On Mon, Apr 1, 2019 at 6:12 AM Dave Crocker <dcrocker@gmail.com> wrote:

> On 3/31/2019 10:57 AM, Viruthagiri Thirumavalavan wrote:
> > I need some clarification about the term "email payload".
>
> The term 'payload' is not a formal term of art in email.  The word
> appears only once in RFC 5598, and not in a context that concerns your
> topic of interest.  It does not appear at all in RFC 5321 or RFC 5322 or
> RFC 3501.
>
> Considering the message body as the payload is reasonable in some cases,
> but not in others, because there is quite a bit of user-to-user
> information in some of the message header fields.
>
> In SMTP context, it's probably safe to say that everything after the
> DATA command is payload.  Certainly in terms of typical use of the word
> payload in protocol discussions, I think that's a straightforward
> assessment.
>
> d/
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>


-- 
Best Regards,

Viruthagiri Thirumavalavan
Dombox, Inc.

v2.23.0 | Report a Bug | By Email