ietf-smtp
[Top] [All Lists]

Re: [ietf-smtp] envelope-to format (was: Re: Fwd: New Version Notification for draft-crocker-email-deliveredto-05.txt)

2021-08-09 19:32:51
On Mon, Aug 09, 2021 at 05:29:07PM -0400, John R. Levine wrote:
If we're speaking of a Delivered-To: header, then no I did not.
Exim does not currently have a specific facility for generating one.

Perhaps you were thinking of my description of Envelope-to:

Right, the header described in draft-crocker-email-deliveredto-05 is in 
fact Envelope-To, not Delivered-To.

Well, yes and no.  On the one hand the subtext seems to be to try to
present a usable envelope recipient address to various tools, but on
the other hand the text is specifically about "Delivered-To" and
includes the loop-detection case.

I keep asking about the motivation for the draft, what problem is
it intended to address...  And yet, the only response I get is
requests to identify specific issues in the text.

But it is not possible to know whether the text is solid or not, unless
I know what the problem being solved is.

I am told the problem statement is in the introduction, but that is
either not the case, or the motivation is too weak to support a useful
draft.  It just states some generalities about how it could be useful
to record the delivery address, with little apparent explanation of
what tangible benefit this brings over existing practice.

Are we trying to make "Delivered-To" loop detection more uniform across
M[TD]As?  Are we trying to support multidrop mailboxes?  Something else?

If there's nothing beyond what's in the draft, then it is about time to
make it clear that it is no experiment, and is just trying to document
current practice.

-- 
    Viktor.

_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp

<Prev in Thread] Current Thread [Next in Thread>