On Wednesday 07 January 2009 07:38, Alessandro Vesely wrote:
Scott Kitterman wrote:
On Wed, 07 Jan 2009 12:22:24 +0100 Alessandro Vesely
<vesely(_at_)tana(_dot_)it>
wrote:
| the key difference between handling aliases (Section 3.9.1) and
| forwarding (this subsection) is the change to the backward-pointing
| address in this case.
The standard literally says that forwarding with a changed return
address is not forwarding. Should that be interpreted like the Baima
Lun saying that a white horse is not a horse?
With a mailing list, a message is sent to the list manager, it is
delivered, and then a new message (with a usually modified body) is
created and sent to the subscriber list.
Why a "new" message? The Message-ID field should be preserved. Even if
the ENVID value should be changed and (positive) DSNs should not reach
the original sender, I wouldn't decorate MTAs with the authorship that
creating a new message requires... Automated body modifications are
also done by clients and MSAs.
So whatever 'forwarding' is, it's pretty clearly not a mailing list.
It was John Klensin who used that term for the action discussed in the
"List" subsection of the standard.
For me, as an MTA admin, the distinction has always been that there's a
delivery. I've no idea how that relates to what's in the current standards
as it's been some time since I looked.
Scott K
-------------------------------------------
Sender Policy Framework: http://www.openspf.org
Modify Your Subscription: http://www.listbox.com/member/
Archives: https://www.listbox.com/member/archive/735/=now
RSS Feed: https://www.listbox.com/member/archive/rss/735/
Powered by Listbox: http://www.listbox.com