[Top] [All Lists]

Re: Lists and aliases (Re: Last Call: draft-klensin-rfc2821bis (Simple Mail Transfer Protocol) to Draft Standard (1))

2007-12-14 10:46:05

Tony Finch wrote:
1.    I believe the 'alias' function refers to a RCPT-TO multi-cast expansion
2a.   Except that the mailing list function can be distinguished by the degree
to which the new message is the same as the original message.  When it is
essentially identical, except for the RCPT-TO list and some additional
handling fields,
2b.   Then there are mailing lists that do some amount of additional violence
to the message, possibly quite a bit.
In which case we should continue to use the term "alias" for type 1, and
we should continue to discourage type 2a lists that don't change the
return path.

I'd like to explore this and see what folk prefer.

I don't have a firm opinion yet. What you suggest makes sense. My question is whether it both resonates with other folk and whether we can see real utility in it (and if so, what?)

For one thing, why is modification of the return path required? I can certainly see legitimate uses of mailing list software (full delivery and then re-posting) which chooses to have notifications go to whatever address is in the original return path.

That, of course, raises the question of whether this use of a mailing list is in any way distinguishable externally from the simpler alias mechanism? That is, does the new message and envelope look different?


  Dave Crocker
  Brandenburg InternetWorking

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