In
<Pine(_dot_)LNX(_dot_)4(_dot_)44(_dot_)0405271711190(_dot_)15973-100000(_at_)bmsred(_dot_)bmsi(_dot_)com>
"Stuart D. Gathman" <stuart(_at_)bmsi(_dot_)com> writes:
I have not yet seen a good answer to why we can't resurrect the reverse
source path.
Hi.
I was out of town for the IETF meeting and then visiting my friends
out in California. I must have missed your earlier post. (I'm pretty
sure Meng has been out of town quite a bit also.)
Both forward and reverse source routing are currently
deprecated but not banned - all MTAs already are required to deal with
them. MTAs are instructed to ignore source routing for purposes of
delivering mail - this is exactly what we want also. All we want is for
forwarders to start including the reverse source route in the envelope
from.
Interesting idea!
Earlier discussions of source routing were about a replacement for
SRS, but since MTAs may or may not ignore the source routing, this
wasn't a real solution.
For the problem of the RFROM/FRED/DAVE ESMTP extention, using source
routing might work. It solves the problem of having *receiving* MTAs
needing to be upgraded and could be deployed immediately.
-wayne