On Tue, 06 May 2003 17:27:21 -0400
Alan DeKok <aland(_at_)freeradius(_dot_)org> wrote:
Now let's look at the problems with the current use of .forward files.
You receive a message from an MTA in example.com, with the envelope &
body "from" being example-2.com.
Forward chained received headers solve the same problem instance, as
well as providing reverse transparency down the full path of the message
(assuming supporting MTAs).
So the solution to .forward files, is to have the forwarding MTA
explicitely declare it's consent to forwarding messages for another
domain.
There's a non-starter in the mailing list world.
In contrast, the simple act of forwarding messages tells you nothing
about consent, other than that forwarding is occuring.
Unless an embedded consent protocol is involved (cf TMDA).
--
J C Lawrence
---------(*) Satan, oscillate my metallic sonatas.
claw(_at_)kanga(_dot_)nu He lived as a devil, eh?
http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg