On Mon, 23 Feb 2004, Daniel Roethlisberger wrote:
> As a general statement about multihop return path rewriting schemes,
I haven't had time to follow this thread, but in case anybody hasn't
noticed, multihop return path rewriting takes us right back to 1982.
This quote is from RFC 821:
The <reverse-path> can contain more than just a mailbox. The
<reverse-path> is a reverse source routing list of hosts and
source mailbox.
and later, this:
Conceptually the elements of the forward-path are moved to the
reverse-path as the message is relayed from one server-SMTP to
another. The reverse-path is a reverse source route, (i.e., a
source route from the current location of the message to the
originator of the message). When a server-SMTP deletes its
identifier from the forward-path and inserts it into the
reverse-path, it must use the name it is known by in the
environment it is sending into, not the environment the mail came
from, in case the server-SMTP is known by different names in
different environments.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book: http://www.uit.co.uk/exim-book
