IETF Logo Mail Archive

Re: [ietf-smtp] Who should set the Sender: header field?

Valdis Kl ē tnieks <valdis.kletnieks@vt.edu> Wed, 15 December 2021 05:16 UTC

Return-Path: <valdis@vt.edu>
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 804BA3A08C2 for <ietf-smtp@ietfa.amsl.com>; Tue, 14 Dec 2021 21:16:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=vt-edu.20210112.gappssmtp.com
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 aiZipe82laPv for <ietf-smtp@ietfa.amsl.com>; Tue, 14 Dec 2021 21:16:02 -0800 (PST)
Received: from mail-qv1-xf35.google.com (mail-qv1-xf35.google.com [IPv6:2607:f8b0:4864:20::f35]) (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 7D34E3A08CD for <ietf-smtp@ietf.org>; Tue, 14 Dec 2021 21:15:55 -0800 (PST)
Received: by mail-qv1-xf35.google.com with SMTP id s9so19270738qvk.12 for <ietf-smtp@ietf.org>; Tue, 14 Dec 2021 21:15:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vt-edu.20210112.gappssmtp.com; s=20210112; h=sender:from:to:cc:subject:in-reply-to:references:mime-version :content-transfer-encoding:date:message-id; bh=V7KJYwYY0g7qXsp17o1D9g0vl5tUmxuRFwfMUUnqyT0=; b=J7Cu0ZV8fa5uB0kexZfbQTnJdH40Vr+wkssDgyqM4YlRK7pzNVrPz8C36ulOAwclVg GKWX9Fy21PAEwzI8mk8t3+qcnEFUsZAUvSL0No4oimTwY4B89IhpMIIhUZvGYH3/8B+D l4LuFddzPnIcTwcrGgUMsUQSqXU9zDw9dM5uOiG7Epd0BiyGF1/D4EtKFeT9u1UOFE7y AsBohDMyzBtguJB+KiSFUkDxeMk1+a6HfPHi10fZQTUowmskxu2+PoxgeAOlbTqu4Jdg /0EoQLdy3ewNnqk2/wa7KAXXU1CZKYlJu3NwOUuP8JQvAle55EO8E9U+dB6fJ/XOD8vt xeDQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:from:to:cc:subject:in-reply-to:references :mime-version:content-transfer-encoding:date:message-id; bh=V7KJYwYY0g7qXsp17o1D9g0vl5tUmxuRFwfMUUnqyT0=; b=lSzVgb2SF7xAGpGGreCAd1jLNbUh3iOKZuaHk09wi1vemU/MktJni6JCds7oFa/ceN d5J0Om7TjSn6prUComvp9yuaecw/8bwXR+K+UAZq9LrXTcPacQNjR8h7eltKkP8905/g /+pU9ae8wSkl3uycJX306blAqIdM+DK4Jx0QyLFVSyUn4ngvmwqmU7P5vhyU6uYg9fb7 aaRSvMmpIEsGW5aSXHP0u4gh9V7GJiseC1yym2CCu335f6eOqNzylKQq9SpI3EMMbXhl D5fNf8FXUdd65gk24veDK568TFy3VJ1x4qTcoCUBtKGGjVZn1dZmZfq2LMckcWJHlYY6 MPjQ==
X-Gm-Message-State: AOAM5328Y17Yz4eLjr96/8S1GVVOGnkMNT/7lu8p9xMLDF8/lBOAbyaF YjYB6CocxreA2ired+M2+5I/B7WupNuB+Q==
X-Google-Smtp-Source: ABdhPJwyCtGsp0HxT2t2dPgu6jlIJx6iUuUAcM5d9IYzcZcpBi5t5zBCF/F8dqpmBryFNGKpCl7k4w==
X-Received: by 2002:a05:6214:22a:: with SMTP id j10mr9443280qvt.104.1639545352183; Tue, 14 Dec 2021 21:15:52 -0800 (PST)
Received: from turing-police ([2601:5c0:c380:d61::359]) by smtp.gmail.com with ESMTPSA id c1sm715694qte.79.2021.12.14.21.15.51 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 14 Dec 2021 21:15:51 -0800 (PST)
Sender: Valdis Kletnieks <valdis@vt.edu>
From: Valdis Kl=?utf-8?Q?=c4=93?=tnieks <valdis.kletnieks@vt.edu>
X-Google-Original-From: "Valdis Klētnieks" <Valdis.Kletnieks@vt.edu>
X-Mailer: exmh version 2.10.0-pre 07/05/2021 with nmh-1.7+dev
To: Alessandro Vesely <vesely@tana.it>
Cc: John Levine <johnl@taugh.com>, ietf-smtp@ietf.org
In-Reply-To: <75f7b99d-e189-7096-bea8-c0da13908393@tana.it>
References: <20211213192454.8BB96315F3E1@ary.qy> <75f7b99d-e189-7096-bea8-c0da13908393@tana.it>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1639545350_15538P"; micalg="pgp-sha256"; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 15 Dec 2021 00:15:50 -0500
Message-ID: <183972.1639545350@turing-police>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/Fkc-0RReAL7QpJ9IOo-I6A4soDk>
Subject: Re: [ietf-smtp] Who should set the Sender: header field?
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: Wed, 15 Dec 2021 05:16:08 -0000

On Tue, 14 Dec 2021 10:27:20 +0100, Alessandro Vesely said:

> Of course, I meant only in case the user added multiple mailboxes to From:.
> RFC 5322 requires that a Sender: field be there in such cases.

I wonder how many of the 800 pound gorillas in the email world still allow
multiple addresses in the From: field - any proposal for weird headers that get
rejected by either Google or Microsoft (rather than silently ignored and passed
along) is de facto DOA, no matter what the de jure status is.

No, I'm not thrilled by this situation, but here we are anyhow.

Which gets me wondering - what *other* "still officially legal but not usable
except in small private conclaves" features are still out there? I know
that nmh/exmh dropped message/partial support because nobody seems
to be using it in the wild...

v2.23.0 | Report a Bug | By Email