----- Original Message -----
From: "Dick St.Peters" <stpeters(_at_)NetHeaven(_dot_)com>
Stuart D. Gathman writes:
There is no forwarding problem in SPF1.
It is true that to correctly check SPF, a receiver that includes
forwarders as
part of their receiving MTA network must take this part of their network
into
account.
There IS a forwarding problem with SPF1, and it has nothing to do with
forwarders as part of a receiving MTA network. It has to do with
forwarding to remote networks.
Dick,
Not to put words into Stuart's mouth, I believe he is basically saying that
to *participate" as a SPF compliant server or receiver you need to make sure
that forwarding isn't a problem.
In other words, a SPF compliant server should not be using a smart host or
routing outbound mail that is not part of the sender's SPF network. He
needs to make sure that when it finally reaches the final destination that
it is still part of the SPF network.
This is what I call transition points. All transition points (hops) in a
SPF network must maintain the IP::DOMAIN SPF association.
Otherwise we have a forwarding problem.
--
Hector Santos, Santronics Software, Inc.
http://www.santronics.com