User Tools

Site Tools


admin:settings:spf

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
admin:settings:spf [2019/04/09 16:18]
csharp
admin:settings:spf [2019/09/25 10:37] (current)
csharp
Line 5: Line 5:
 Fortunately,​ there is a mechanism your library can use to tell patrons'​ email providers'​ servers to consider messages sent from gapines.org to be legitimate: [[http://​www.openspf.org/​Introduction|Sender Policy Framework]],​ or SPF.  An SPF entry is set up by whoever manages your email domain. ​ For example, if your library'​s email domain is "​georgialibraries.org"​ you could use [[http://​www.kitterman.com/​spf/​validate.html]] and enter "​georgialibraries.org"​ into the "​domain"​ field. ​ You would see something like the following: Fortunately,​ there is a mechanism your library can use to tell patrons'​ email providers'​ servers to consider messages sent from gapines.org to be legitimate: [[http://​www.openspf.org/​Introduction|Sender Policy Framework]],​ or SPF.  An SPF entry is set up by whoever manages your email domain. ​ For example, if your library'​s email domain is "​georgialibraries.org"​ you could use [[http://​www.kitterman.com/​spf/​validate.html]] and enter "​georgialibraries.org"​ into the "​domain"​ field. ​ You would see something like the following:
  
-<wrap indent>​v=spf1 include:​_spf.google.com ip4:64.57.241.9 ip4:​64.57.241.6</​wrap>​\\ +<wrap indent>​v=spf1 include:​_spf.google.com ip4:168.28.68.41 ~all</​wrap>​
-<wrap indent>​ip4:​64.57.241.17 ​~all</​wrap>​+
  
 This is the SPF entry for that domain. ​ Here's a breakdown of what each part means: This is the SPF entry for that domain. ​ Here's a breakdown of what each part means:
Line 14: Line 13:
 | v=spf1 ​                  | The SPF version being used                                                     | | v=spf1 ​                  | The SPF version being used                                                     |
 | include:​_spf.google.com ​ | "​include the SPF record for the '​_spf.google.com'​ domain" ​                     | | include:​_spf.google.com ​ | "​include the SPF record for the '​_spf.google.com'​ domain" ​                     |
-| ip4:64.57.241.         | "​consider ​64.57.241.to be a valid sending IP address" ​                       ​+| ip4:168.28.68.41          | "​consider ​168.28.68.41 to be a valid sending IP address" ​                       |
-| ip4:​64.57.241.6 ​         | "​consider 64.57.241.6 to be a valid sending IP address" ​                       | +
-| ip4:​64.57.241.17 ​        | "​consider 64.57.241.17 to be a valid sending IP address" ​                      |+
 | ~all                     | "if anything above hasn't matched, mark it 'soft failure'​ but let it through" ​ | | ~all                     | "if anything above hasn't matched, mark it 'soft failure'​ but let it through" ​ |
  
 As of April 11, 2019, PINES' sending IP addresses are 168.25.131.21 (primary) and 168.25.131.22 (failover), so they will need to be added to the SPF record for georgialibraries.org sending addresses to be accepted. ​ Our edited SPF record would then look like this: As of April 11, 2019, PINES' sending IP addresses are 168.25.131.21 (primary) and 168.25.131.22 (failover), so they will need to be added to the SPF record for georgialibraries.org sending addresses to be accepted. ​ Our edited SPF record would then look like this:
  
-<wrap indent>​v=spf1 include:​_spf.google.com ip4:64.57.241.9 ip4:​64.57.241.6</​wrap>​\\ +<wrap indent>​v=spf1 include:​_spf.google.com ip4:168.28.68.41 ip4:​168.25.131.21 ip4:​168.25.131.22 ~all</​wrap>​
-<wrap indent>​ip4:​64.57.241.17 ​ip4:​168.25.131.21 ip4:​168.25.131.22 ~all</​wrap>​+
  
 With that in place, messages should be accepted by email providers that consult the SPF record. ​ You would want to ask whoever manages your email to make that change. ​ NOTE:  GPLS-hosted email has already made this change, so no further action is required. ​ With that in place, messages should be accepted by email providers that consult the SPF record. ​ You would want to ask whoever manages your email to make that change. ​ NOTE:  GPLS-hosted email has already made this change, so no further action is required. ​
admin/settings/spf.txt · Last modified: 2019/09/25 10:37 by csharp