Dave Crocker writes:
On 8/4/2021 4:29 PM, Sam Varshavchik wrote:
Delivered-To: mrsam(_dot_)virtual(_at_)monster(_dot_)email-scan(_dot_)com
Return-Path: <postmaster(_at_)monster(_dot_)email-scan(_dot_)com>
Received: from monster.email-scan.com (localhost [::1])
by monster.email-scan.com with ESMTP
id 0000000000068359.00000000610B21CB.00014A01; Wed, 04 Aug 2021 19:24:44
-0400
Subject: test
From: postmaster(_at_)monster(_dot_)email-scan(_dot_)com
To: postmaster(_at_)monster(_dot_)email-scan(_dot_)com
Subject: local mail
test
The Delivered-To: header has nothing to do with the SMTP recipient. This
node owns @monster.email-scan.com, and it's up to this node to decide what
goes in there.
The revised draft's language tries to cover this. Please review.
I looked at the document diff. Wording in several places was revised along
these lines:
Old: "The header field contains the individual mailbox.."
New: "The header field contains information about the individual mailbox.."
This kind of change was consistent in several place, but in one instance –
which I noticed before – the old phrasing remained:
"Delivered-To:" FWS *phrase Mailbox *phrase CRLF
; Mailbox is from [SMTP]
Note: The field records only a single mailbox, for one recipient.
It would be more consistent for this to also be updated to:
Note: The field records information about only a single mailbox, for
one recipient.
pgpQ6ZNQKPd4b.pgp
Description: PGP signature
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp