No, it'll tell them that joe's email address sent the spam,
and that it must have come through a machine allowed to
send email from joe's domain.
If you don't think that's the same thing... Kudos to you. But I think most
people will think "It was authorized to come from joe(_at_)joe(_dot_)com, so
unless the
authorization process is hacked, Joe really sent it."
I don't think the end users have any clue right now,
and they won't later either.
Some know that addresses are forgable, but only because
viruses have been doing it. Others already think that
no one can possibly forge an address.
SPF won't change their views at all. If they hear
anything about SPF, all they'll think is that it will
help there be less spam, and that a bunch of geeks
are around who know what's going on.
--
Brian Hatch A journey of a
Systems and thousand miles
Security Engineer begins with a
http://www.ifokr.org/bri/ cash advance.
Every message PGP signed
-------
Sender Permitted From: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
Latest draft at http://spf.pobox.com/draft-mengwong-spf-02.9.4.txt
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname(_at_)½§Åv¼ð¦¾Øß´ë ù1Ií-»Fqx(_dot_)com
pgp1M9eEms7bR.pgp
Description: PGP signature