Home | Sitemap | Recent Changes | Login

SPF Logo

Sender Policy Framework

History of Community/Sandbox


Revision 53 . . 2013-05-23 19:26 (UTC) by xyzzy [EAGAIN, #41 was good, #42 was already contaminated]
Revision 52 . . (edit) 2013-05-23 19:24 (UTC) by xyzzy [rvv]
Revision 51 . . 2013-05-22 7:36 (UTC) by grosirbaju
Revision 50 . . (edit) 2013-05-08 21:33 (UTC) by xyzzy [rv spam to #42]
Revision 49 . . 2013-05-08 15:50 (UTC) by Mlio
Revision 48 . . (edit) 2013-03-10 14:30 (UTC) by sgtop
Revision 47 . . (edit) 2013-03-10 14:25 (UTC) by sgtop
Revision 46 . . (edit) 2013-03-10 14:25 (UTC) by sgtop
Revision 45 . . (edit) 2013-03-10 14:24 (UTC) by sgtop
Revision 44 . . (edit) 2013-03-10 14:22 (UTC) by sgtop
Revision 43 . . (edit) 2013-03-10 14:21 (UTC) by sgtop
Revision 42 . . (edit) 2012-05-14 16:27 (UTC) by FunnySayings [added explanatory section on the old record wizard]
Revision 41 . . 2008-04-15 7:30 (UTC) by ale [append nowiki vs. code ]
Revision 40 . . 2007-03-04 5:01 (UTC) by Alex [reordered sender and receiver side; elaborated on include;typos]
Revision 39 . . 2007-03-01 16:57 (UTC) by Alex
Revision 38 . . 2007-03-01 16:46 (UTC) by Scott Kitterman [Minor edits on proposed new why page]
Revision 37 . . 2007-03-01 16:26 (UTC) by Alex
Revision 36 . . 2007-02-28 20:33 (UTC) by Alex
Revision 35 . . 2007-02-28 16:24 (UTC) by Alex
Revision 34 . . (edit) 2007-02-28 4:41 (UTC) by Alex
Revision 33 . . 2007-02-28 3:53 (UTC) by Alex
Revision 32 . . 2007-02-28 3:51 (UTC) by Alex
Revision 31 . . 2007-02-28 3:46 (UTC) by Alex
Revision 30 . . 2007-02-26 3:45 (UTC) by ukperlprogrammer
Revision 29 . . 2007-02-20 20:26 (UTC) by Alex van den Bogaerdt
Revision 28 . . 2007-02-20 17:18 (UTC) by Alex
Revision 27 . . 2007-02-20 17:09 (UTC) by Alex
Revision 26 . . 2007-02-20 17:06 (UTC) by Alex
Revision 25 . . 2007-02-19 18:15 (UTC) by Alex
Revision 24 . . 2007-02-19 18:06 (UTC) by Alex
Revision 23 . . 2007-02-19 17:15 (UTC) by Alex
Revision 22 . . 2007-02-19 17:05 (UTC) by Alex
Revision 21 . . 2007-02-18 17:44 (UTC) by Alex
Revision 20 . . 2007-02-18 17:40 (UTC) by Alex
Revision 19 . . 2007-02-18 17:22 (UTC) by Alex
Revision 18 . . (edit) 2007-01-18 21:29 (UTC) by stk
Revision 17 . . (edit) 2007-01-18 21:24 (UTC) by stk
Revision 16 . . 2007-01-18 17:04 (UTC) by stk
Revision 15 . . 2007-01-18 16:52 (UTC) by stk
Revision 14 . . (edit) 2007-01-17 16:55 (UTC) by stk
Revision 13 . . (edit) 2007-01-16 19:59 (UTC) by stk
Revision 12 . . (edit) 2007-01-16 19:57 (UTC) by stk
Revision 11 . . 2007-01-16 19:45 (UTC) by stk [A Randsco Rant]
Revision 10 . . 2006-03-11 21:00 (UTC) by kitterma
Revision 9 . . 2006-03-11 20:58 (UTC) by kitterma
Revision 8 . . 2005-11-05 6:15 (UTC) by xyzzy [Fix broken example. Use link working without authorization.]
Revision 7 . . 2005-11-04 10:25 (UTC) by Julian Mehnle
Revision 6 . . (edit) 2005-11-04 8:21 (UTC) by xyzzy
Revision 5 . . 2005-11-04 8:15 (UTC) by xyzzy [Test new subpage]
Revision 4 . . 2005-09-13 15:07 (UTC) by willix
Revision 3 . . 2005-09-13 15:07 (UTC) by willix
Revision 2 . . (edit) 2005-09-04 6:15 (UTC) by test [Testing is fun]
Revision 1 . . 2005-08-15 2:14 (UTC) by Julian Mehnle (unauthenticated) [created page]
  

Difference (from prior major revision) (author diff)
Paragraph 6Paragraph 6

A link to a new <code>[[Community/subpage|page]]</code> [[Community/subpage|page]] creates a new page of [http://www.thefunnyquotessayings.com/dr-sheldon-cooper-quotes-the-big-bang-theory/ the big bang theory quotes].

A link to a new <code>[[Community/subpage|page]]</code> [[Community/subpage|page]] creates a new page.

Paragraph 10Paragraph 10

SPF has two parts: one for the sender, and one for the receiver.  If everybody published an SPF policy, but nobody would use these policies, then nothing is going to happen.  If you want others to pay attention to your SPF record, you can understand that others want you to pay attention to theirs.  This is why you should do both parts! (if possible)[http://itshumour.blogspot.com/2010/02/top-five-hilarious-videos-on-youtube.html hilarious videos]

SPF has two parts: one for the sender, and one for the receiver.  If everybody published an SPF policy, but nobody would use these policies, then nothing is going to happen.  If you want others to pay attention to your SPF record, you can understand that others want you to pay attention to theirs.  This is why you should do both parts! (if possible)

Paragraph 16Paragraph 16

* you need to be able to publish your SPF policy in DNS [http://bit.ly/dt3ruz funny quotes]

* you need to be able to publish your SPF policy in DNS

Paragraph 29Paragraph 29

;MX : If you have a lot of computers receiving mail for you [http://goo.gl/PKsQv funny jokes], and if all of them also send mail for you, then you could choose to use this mechanism. But don't use it if you have only one computer that does all work, and don't use it if you have more than ten.  I guess this means most people should <strong>not</strong> be using this mechanism.

;MX : If you have a lot of computers receiving mail for you, and if all of them also send mail for you, then you could choose to use this mechanism. But don't use it if you have only one computer that does all work, and don't use it if you have more than ten.  I guess this means most people should <strong>not</strong> be using this mechanism.

Paragraph 38Paragraph 38

If you know the provider has setup something for you to include, most will give you advice on how to do so.  This advice is well ment but often wrong; they have no way of knowing how your record should look like.  Use their example as an example only, not as something you can cut and paste.  Or just read this text...[http://www.thefunnyquotessayings.com/funny-classroom-jokes-for-kids/ funny jokes kids]

If you know the provider has setup something for you to include, most will give you advice on how to do so.  This advice is well ment but often wrong; they have no way of knowing how your record should look like.  Use their example as an example only, not as something you can cut and paste.  Or just read this text...

Paragraph 56Paragraph 56

Same kind of office, but with a dynamic IP address.  In stead of changing the policy each time a new connection is made, it is acceptable to use the server's name in this case.  PROBLEM: chances are the name will also change, as it will be based on the IP address being used.  Your best bet is to use another server, for example one at your ISP, or for instance dyndns.  I will show an example for dyndns [http://www.thefunnyquotessayings.com/cool-hilarious-funny-quotes-sayings/ funny quotes sayings], not because I want to recommend their service but just because I need an example.  Dyndns has specified in their FAQ how they have created a policy for you to include.  Great news, just "include:outbound.mailhop.org".  Prefix is "v=spf1", suffix is "-all", complete policy is "v=spf1 include:outbound.mailhop.org -all".

Same kind of office, but with a dynamic IP address.  In stead of changing the policy each time a new connection is made, it is acceptable to use the server's name in this case.  PROBLEM: chances are the name will also change, as it will be based on the IP address being used.  Your best bet is to use another server, for example one at your ISP, or for instance dyndns.  I will show an example for dyndns, not because I want to recommend their service but just because I need an example.  Dyndns has specified in their FAQ how they have created a policy for you to include.  Great news, just "include:outbound.mailhop.org".  Prefix is "v=spf1", suffix is "-all", complete policy is "v=spf1 include:outbound.mailhop.org -all".