Gentoo Archives: gentoo-commits

From: "Robin H. Johnson (robbat2)" <robbat2@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/en/infrastructure: spf.xml
Date: Mon, 23 Aug 2010 18:59:49
Message-Id: 20100823185945.18FCC2004C@flycatcher.gentoo.org
1 robbat2 10/08/23 18:59:45
2
3 Modified: spf.xml
4 Log:
5 Finish style cleanup of SPF reasoning doc.
6
7 Revision Changes Path
8 1.6 xml/htdocs/proj/en/infrastructure/spf.xml
9
10 file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/infrastructure/spf.xml?rev=1.6&view=markup
11 plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/infrastructure/spf.xml?rev=1.6&content-type=text/plain
12 diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/en/infrastructure/spf.xml?r1=1.5&r2=1.6
13
14 Index: spf.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/infrastructure/spf.xml,v
17 retrieving revision 1.5
18 retrieving revision 1.6
19 diff -p -w -b -B -u -u -r1.5 -r1.6
20 --- spf.xml 23 Aug 2010 18:37:55 -0000 1.5
21 +++ spf.xml 23 Aug 2010 18:59:45 -0000 1.6
22 @@ -12,7 +12,7 @@
23 <abstract>
24 This guide documents some of the reasons why (and how) Gentoo utilizes SPF.
25 </abstract>
26 -<version>1.2</version>
27 +<version>1.3</version>
28 <date>2010-08-23</date>
29
30 <chapter>
31 @@ -46,7 +46,7 @@ those servers.
32 For Gentoo, our SPF record is currently:
33 </p>
34 <pre caption="gentoo.org SPF record">
35 -"v=spf1 mx ptr ?all"
36 +v=spf1 mx ptr ?all
37 </pre>
38
39 <p>
40 @@ -58,18 +58,18 @@ Which breaks down as:
41 <dt>?all</dt> <dd>if you receive an email from an MTA not on this list, please treat it neutrally. (i.e. do not make decisions based solely on this fact)</dd>
42 </dl>
43 <p>
44 -The ?all is intended to be a transitional phase, with the ultimate goal being
45 -to move to ~all or even -all, which are more definitive.
46 +The <c>?all</c> is intended to be a transitional phase, with the ultimate goal being
47 +to move to <c>~all</c> or even <c>-all</c>, which are more definitive.
48 </p>
49 <p>
50 Some people have objected to the fact that SpamAssassin adds ~1 to the overall
51 -spam score for ?all records. SPF is a tool and, like any other tool, people
52 -can do smart things with it and they can do stupid things with it. I'm not
53 -saying the SA guys are stupid -- merely that they've chosen to use the tool a
54 -certain way that conflicts with what the SPF standard calls for. As you can
55 -tell from the SA test name (SPF_NEUTRAL), SPF calls for records using ?all to
56 -treat MTAs sending mail on behalf of that domain neutrally. SPF should not be
57 -faulted if SA chooses to go another route.
58 +spam score for <c>?all</c> records. SPF is a tool and, like any other tool,
59 +people can do smart things with it and they can do stupid things with it. This
60 +is not saying the SA developers are stupid -- merely that they've chosen to use
61 +the tool a certain way that conflicts with what the SPF standard calls for. As
62 +you can tell from the SA test name (SPF_NEUTRAL), SPF calls for records using
63 +<c>?all</c> to treat MTAs sending mail on behalf of that domain neutrally. SPF
64 +should not be faulted if SA chooses to go another route.
65 </p>
66 <p>
67 SA provides users with ways of overriding or ignoring this score on a per-user
68 @@ -110,14 +110,16 @@ To: john@×××.com
69 Subject: check spam scores
70 </pre>
71 <p>
72 -which shows a mythical developer sending an email From: johndoe@g.o
73 +which shows a mythical developer sending an email <c>From: johndoe@g.o</c>
74 using his gmail account. Note that the SA score is actually reduced due to SPF
75 in this particular case.
76 -
77 +</p>
78 +<p>
79 Additionally, as has been the case for months, we allow developers to relay
80 (via aSMTP) their outbound gentoo.org mail through dev.gentoo.org if they so
81 choose, which also works around the specific issue with SA.
82 -
83 +</p>
84 +<p>
85 Again, SPF is a tool. Nothing more, nothing less. All we do is provide
86 information to other mail administrators. How they decide to use it is up to
87 them.