On Wed, Jul 06, 2005 at 12:23:16PM -0400, Dick St.Peters wrote:
<quote>
In both the enterprise and the "new address" cases, information
hiding (and sometimes security) considerations argue against exposure
of the "final" address through the SMTP protocol as a side-effect of
the forwarding activity. This may be especially important when the
final address may not even be reachable by the sender.
</quote>
You are warping a statement about protecting the *destination* address
into an argument about the *sender* address. It doesn't apply.
Yes it does. Bounces are sent to the sender address.
If you start using a forwarding service because you don't want me
to know your real address (for whatever reason) (yes, this happens)
you don't want bounces to reach me. Bounces will show your real
address, not your forwarding address. I also said this is a problem
of forwarders, unrelated to SPF.
RFC2821 does have this to say though, in section 4.1.1.3:
<quote>
For example, mail received at relay host xyz.com with envelope
commands
MAIL FROM:<userx(_at_)y(_dot_)foo(_dot_)org>
RCPT TO:<@hosta.int,@jkl.org:userc(_at_)d(_dot_)bar(_dot_)org>
will normally be sent directly on to host d.bar.org with envelope
commands
MAIL FROM:<userx(_at_)y(_dot_)foo(_dot_)org>
RCPT TO:<userc(_at_)d(_dot_)bar(_dot_)org>
</quote>
Yes it will. The originating server will deliver it to d.bar.org,
not a forwarding server (such as hosta.int). Your point being?
Alex