-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Wayne Schlitt wrote:
When people sign up for the spf-discuss list, the get a welcome
message. This morning I updated it slightly to no longer mention
things like spf.pobox.com, the "SPF wiki" on infinitepenguins, and a
few other minor things.
Below is the current text. Please let me know what changes, if any,
that people think should be made.
Here's a revision based on yours. It has a few minor grammar and URL fixes
and additions, adds news about the SPF RFC, and is rewrapped at 74
columns:
- --------8<----snip----8<----snap----8<--------
This list is for open discussion of the SPF e-mail anti-forgery system.
Subscription to this list, and posting to it, is a privilege, not a right.
The list operates according to the best practices described in RFC 1855.
Please review <http://www.ietf.org/proceedings/02mar/slides/plenary-3/>,
too.
Revocation of privileges operates according to an abbreviated form of
BCP83. In short: kooks, crazy people, and rude people should expect to be
unsubscribed.
The SPF mailing list is intended for constructive discussion and promotion
of SPF. If you believe that the SPF concept is fundamentally flawed,
please read the discussion archives at
<http://archives.listbox.com/spf-discuss> or
<http://dir.gmane.org/gmane.mail.spam.spf.discuss> (searchable)
as your point has almost certainly been discussed at length before.
Rehashing old arguments, especially in a combative way, may be considered
rude by most people. New arguements, or new information about old
arguments, however, are quite welcome.
ABOUT SPF
The SPF standard originated as a hybrid of Gordon Fecyk's DMP proposal and
Hadmut Danisch's RMX proposal. It now provides a superset of their
functionality. Find more information at <http://www.openspf.org>.
May 2006: The SPF specification has been published as RFC 4408 by the
IETF: <http://new.openspf.org/News/SPFv1_is_RFC_4408>
November 2004: The Messaging Anti-Abuse Working Group (MAAWG)
sponsors a white paper titled Sender Authentication: What To Do
<http://www.openspf.org/whitepaper.pdf>. Please read it!
October 2004: Microsoft encourages the publication of SPF records.
Microsoft will use a modified form of SPF, known as "Sender ID", to
check message headers in MUAs. Most other MTA implementations
continue to use SPF in its original form, to check the return-path at
SMTP time. Learn more about the differences between SPF and S-ID:
<http://new.openspf.org/SPF_vs_Sender_ID>
Official announcements regarding SPF will be made on this list and also on
the announcements-only list, spf-announce(_at_)v2(_dot_)listbox(_dot_)com, so
you don't
need to subscribe to both lists.
FOR DOMAIN OWNERS
SPF is now ready for widespread adoption. If you control a domain (i.e.,
if you can add DNS entries for the domain), you should publish SPF records
for it now. You can get started at <http://www.openspf.org/wizard.html>.
It takes most people about 10 minutes to learn about SPF and 5 minutes to
write the records.
FOR MAIL ADMINS
You can download plugins for Postfix, Exim, Qmail, Sendmail, Exchange, and
other MTAs from <http://new.openspf.org/Implementations>.
FOR DEVELOPERS
One of SPF's design goals is to be simple, quick, and easy for domain
owners to publish records. We have met this goal at the cost of some
complexity on the client end. Most developers accept this tradeoff.
There are SPF libraries for various programming languages ready for easy
integration into existing or new software products:
<http://new.openspf.org/Implementations>
- -------->8----snip---->8----snap---->8--------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFSosLwL7PKlBZWjsRAq6AAKC2NoTcmgGUdgmcz3q3OLcUAVERkACghgvz
PzZmskYy5APazhaUlIGJn1c=
=Hgr3
-----END PGP SIGNATURE-----
-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com