On Wed, 22 Jun 2005, Hector Santos wrote:
In my view, you will have no choice but to do something with 2822 headers
to address the forwarding problem in SPF1.
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.
If this is too hard because they have never paid attention while adding 3rd
party MTAs willy nilly to their MTA network over the last 10 years, then they
don't have to check SPF, or if they do, they don't have to reject
any mail based on a FAIL. They can still publish SPF.
An SPF publisher may have trouble if they habitually send mail
from random IPs at hotel ISPs, and may need to publish ?all until they
get SMTP AUTH configured and their sending MTA network cleaned up.
In the same way, an SPF receiver may not be able to actually reject
anything based on SPF until they get their receiving MTA network cleaned up,
and configure SRS or whitelisting for all their forwarders.
Forwarding with SPF is trivial if you have control of your network to begin
with. If you don't have control of your network, then you have much worse
problems than no being able to reject based on SPF.
--
Stuart D. Gathman <stuart(_at_)bmsi(_dot_)com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flamis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.