> > The issue I addressed was the supposed SPF forwarder problem.
> > There is no such problem. Once a message is no longer directed
> > to the original RFC2821.RcptTo, the message was delivered.
> >
> Unfortunately, that's not quite true.
>
What isn't?
"There is not such problem".
By declaring that the message has been delivered, prior to alias re-submission,
we are not done.
> > When the "Source" is faked to be the original rfc2821.mailfrom,
> >
> MailFrom does not specify Source.
>
Sure. "Source", not Source. The forwarder pretends that the original
responsible person or other kind of entity, in other words the return
address as set by the original Source, has not changed. It may have
been better not to try and use shorthand. Sorry.
RFC2821.MailFrom specifies a return (bounce, notification, ...) address, not a
source address.
It is "set by" the rfc2821.sender, but does not specify a source. The
difference is quite important.
And having the MailFrom specify some other address is not "forgery" as folks
often call it.
d/
--
Dave Crocker
Brandenburg InternetWorking
+1.408.246.8253
dcrocker a t ...
WE'VE MOVED to: www.bbiw.net