Re: [ietf-smtp] homework, not an experiment, draft-crocker-email-deliver

It appears that Dave Crocker  <dcrocker(_at_)bbiw(_dot_)net> said:
> On 8/3/2021 10:10 PM, Viktor Dukhovni wrote:
> > In Postfix, the address that is presently recorded is the result of any
> > internal rewriting such as mapping"First(_dot_)Last(_at_)example(_dot_)com"  
> > to some internal
> > "uid(_at_)mailstore1(_dot_)example(_dot_)com", that may not correspond to 
> > any public address
> > of the recipient. ...
> >    "Delivered-To:" FWS Mailbox CRLF
> >                     ; Mailbox is from [SMTP]
The thing after the FWS is an opaque token. Sometimes it may look like
a mailbox, sometimes not. And even if it looks like a mailbox, it
often is *not* a mailbox. You can't use it for delayed running of
procmail or redelivery via fetchmail or anything else that expects a
mailbox.

As a concrete example, if you send mail to johnl(_at_)taugh(_dot_)com, here's 
the Delivered-To

 Delivered-To: virtual-taugh-johnl(_at_)taugh(_dot_)com

That pseudo-address reflects the detailf of my mail set up, but if you or I
tried to send mail to it, it wouldn't work. 

It would make sense for us to do a survey of MTAs and describe how they 
actually use
Delivered-To and write it up, which is a report rather than an experiment.  
Take a look
at RFC 7085 in which Paul Hoffman and I did a survey of TLD apex DNS records 
for what I mean.

R's,
John

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