Re: loop homework, not an experiment, draft-crocker-email-deliveredto

Wow this thread goes long...

Unlimited Delivered-To: can be added as trace headers, and SOME systems 
will consider if a Delivered-To: token that already exists, is in a 
loop, a 'convenience' of having that trace header in place.  (Other 
systems may use alternative methods of loop tracing, using their own 
methods, and possibly other headers)

Delivered-To: once again, is SIMPLY a trace header, when a MTA hands off 
the message to a system that 'should' know how to handle the message for 
final handling/distribution.

So, RFC's should simply note that it is a trace header, should be added 
to the top of trace headers,period.

.. with a 'side note' that many existing systems assume the token in a 
single Delivered-To: will be unique during the processing of a message, 
and MAY consider an existing Delivered-To: + token as representing a loop.



On 2021-08-07 9:22 a.m., Ned Freed wrote:
> Not quite getting it.
> 
> A single token describes all of the recipients? Or do you simply 
> generate more
> than one Delivered-to: in the same message?
> 
> Let's make this concrete. We have these aliases:
> 
> alias1: local-recipient-1, local-recipient-2
> 
> alias2: remote-recipient-1, remote-recipient-2
> 
> How many message copies do these generate, and what fields are added?
> 
> And while we're at it, what does
> 
> alias3: alias3, extra-recipient-1
> 
> do?



-- 
"Catch the Magic of Linux..."
------------------------------------------------------------------------
Michael Peddemors, President/CEO LinuxMagic Inc.
Visit us at http://www.linuxmagic.com @linuxmagic
A Wizard IT Company - For More Info http://www.wizard.ca
"LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd.
------------------------------------------------------------------------
604-682-0300 Beautiful British Columbia, Canada

This email and any electronic data contained are confidential and intended
solely for the use of the individual or entity to which they are addressed.
Please note that any views or opinions presented in this email are solely
those of the author and are not intended to represent those of the company.