At 11:15 PM 03/04/2003 -0500, Derek J. Balling wrote:
On Tuesday, March 4, 2003, at 11:10 PM, Troy Rollo wrote:
This breaks automated forwarding.
Couple solutions to that, most of which are documented pretty well in
Gordon's proposal ( http://www.pan-am.ca/draft-ietf-asrg-dsprotocol-00.txt ).
Actually it says "Another document will identify similar problems and
solutions, including mail forwarding services and the Null Sender envelope
(MAIL FROM:<>)."
The problem is that this approach assumes that the only significant reason
mail with a given domain can come from a location not in a pre-authorised
set is that it's spam. I would submit that there are many more common
reasons for mail coming from an unexpected source - forwarding just being
an immediately obvious one.
Even for forwarding, authorising the re-sending host at the receiving end
requires at its best that the user provide this information (perhaps by
means of some web based form) to the receiving ISP, and assumes that:
(1) The user can get it right.
(2) The user has access to all of the relevant information.
(3) That the user knows within a reasonably short period (
or preferably in advance) when the information changes.
None of these is a particularly good assumption.
--
Troy Rollo Chairmain, CAUBE.AU
asrg(_at_)troy(_dot_)rollo(_dot_)name Executive Director, iCAUCE
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg