IETF Logo Mail Archive

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

Viruthagiri Thirumavalavan <giri@dombox.org> Sun, 31 March 2019 18:25 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 AA67D120021 for <ietf-smtp@ietfa.amsl.com>; Sun, 31 Mar 2019 11:25:38 -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 S2K6XL8bueiW for <ietf-smtp@ietfa.amsl.com>; Sun, 31 Mar 2019 11:25:37 -0700 (PDT)
Received: from mail-yw1-xc36.google.com (mail-yw1-xc36.google.com [IPv6:2607:f8b0:4864:20::c36]) (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 0DB5212001B for <ietf-smtp@ietf.org>; Sun, 31 Mar 2019 11:25:36 -0700 (PDT)
Received: by mail-yw1-xc36.google.com with SMTP id l5so2487240ywa.0 for <ietf-smtp@ietf.org>; Sun, 31 Mar 2019 11:25:36 -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=20Fz+ELHFrOzzharNRVTFGiJJJKt2rv+agjIMlcV+h4=; b=mTy41WWRF8JBow41ZZdRbMj4/5rN8DpJaifDiqU1jQCnWyhdM9QoUQCEOVqvDEx7ae ThGwz7dXrcM8o0E7TvaGn1Iqmz6umOd51EumgtiV4Csux47jWBfnMnH31TY/yCZtTB5g pmcltvwXpDTSpNhsctAWPGGQjP944/zXLWCjL5mV+lraJJ+FXBZr4KivzyxWFRZQcT5I E4mLc7T4vjDeOF+UMGdL6e5Xx/2Hv0/y9/0yPCRxw9hKbkzx4D0+MAXBH/FFWz27aGgW sbU53DSMUbhSkn4H4X2KwOtPHsdqTQxOpSyiFP/zeuCV4bwpSFpzrz/HNy+6o+nzjLJ9 Ar8A==
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=20Fz+ELHFrOzzharNRVTFGiJJJKt2rv+agjIMlcV+h4=; b=lmISfYBC56wUi1ZLnB9hVCQFb6DLmTCapyhBER3UTk/Gv+mdRJSAW3kgkO2nq5GC26 P9fm6wj1GwAIoFFuOl5eHMkti6WJcoGGIfgeiR8ASWA3lEcjiO/itLedvqcJTQDavyBl iQp0G3oU04lMhm37/6y7xSwSX1wJJUHWu8At8jp4+gpvlMZBYAs1Apv90gU7bMKqHjHY vD39hxOv2hosDzf5Y08XP7UKkcoTmy0GORIvpEDod43qhMi2Xjw28wEgtQ5VLFtCmPGZ 1fSRewIdsUfT8ZlZC7m8MrPGGRAs2Gz0EjmeO9uzG/V/sm7LVbDO7YuLbOVZy97cZ3hZ V1SQ==
X-Gm-Message-State: APjAAAUWNZx9/yZYrt25ibh4CHJhIUcf+q/IdwDys3AAgLJTqWwb4YHU A1tmAahxqGjJhpB+2o3XGXSWqqUMsm384TX7BQ0HYA==
X-Google-Smtp-Source: APXvYqxsz9q2x6IOrjB22rvOTc+mUs1m6my4E/PDWMw1yFdw0VJY1I4PFaovXfzbUNCxZIE0a0Di9ZLGRH6Oo/IETew=
X-Received: by 2002:a0d:dbd7:: with SMTP id d206mr50967024ywe.332.1554056736026; Sun, 31 Mar 2019 11:25:36 -0700 (PDT)
MIME-Version: 1.0
References: <CAOEezJRM8ZVaWK6rtvP4ZH9CbN-itVof9_Zi8hf+wVym0cAxzA@mail.gmail.com> <cfbc2ac9-3599-b71b-7d35-7765db7ac81a@network-heretics.com>
In-Reply-To: <cfbc2ac9-3599-b71b-7d35-7765db7ac81a@network-heretics.com>
From: Viruthagiri Thirumavalavan <giri@dombox.org>
Date: Sun, 31 Mar 2019 23:55:00 +0530
Message-ID: <CAOEezJQn4g4m4J+J-AdkjnR-uwusLDgcj+9MQjv4hNFZjaz0Zg@mail.gmail.com>
To: Keith Moore <moore@network-heretics.com>
Cc: ietf-smtp@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b64448058568072f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/0IOzlGK8PhDCtyfcvs0f-1cHOkA>
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:25:39 -0000

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

On Sun, Mar 31, 2019 at 11:40 PM Keith Moore <moore@network-heretics.com>
wrote:

> On 3/31/19 1:57 PM, Viruthagiri Thirumavalavan wrote:
>
> > Hello IETF,
> >
> > I need some clarification about the term "email payload".
>
> IMO, the term "email payload" is not well-defined, and is therefore
> ambiguous and should not be used whenever precision is needed.
>
> The terms header and body are well-defined.
>
> Keith
>
>
> _______________________________________________
> ietf-smtp mailing list
> ietf-smtp@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-smtp
>


-- 
Best Regards,

Viruthagiri Thirumavalavan
Dombox, Inc.

v2.23.0 | Report a Bug | By Email