-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Stuart D. Gathman wrote:
On Wed, 13 Jul 2005, wayne wrote:
I talked with Harry Katz of Microsoft at the email authentication
summit on Tuesday. He said that Microsoft is also trying to contact
domain owners with broken records and try to get them fixed.
I mentioned the expedia.com case, and he wrote it down to make sure
that it would get fixed.
I think this is an area where we can work with MS.
Until they start contacting domain owners with correct SPF records that
fail with senderID.
Much as I hate to say it, I think the solution is to publish spf2.0/pra
in parallel with v=spf1 records. I realize it is beyond the specified
interests of this group, but I think the real solution is to face the
problem head-on and come up with a useful recommendation for validating
2822 From ourselves.
Say something like:
example.com SPF "v=spf1 a mx -all"
SPF "v=spf3 scope=from validmfrom=example.com\
validmfrom=partner.example.net -all"
- --
Daniel Taylor VP Operations Vocal Laboratories, Inc.
dtaylor(_at_)vocalabs(_dot_)com http://www.vocalabs.com/
(952)941-6580x203
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFC1oYP8/QSptFdBtURAgioAJ9dIq6BVI/5VHioJJN1PCbjKw5dJACbB8DS
TylzDCU0SFvf1P3EVmVuf/o=
=Towz
-----END PGP SIGNATURE-----