Re: misconception in SPF
Christian Grunfeld <[email protected]>
| Newsgroups | gmane.ietf.asrg |
|---|---|
| Message-ID | <CAFdugakaY6Lh_5HR8xN7YqrimO9nM72mpxtLwE7T0CpKFu75tA@mail.gmail.com> |
2012/12/10 Chris Lewis <[email protected]>: > You mean like this? > > _spf.google.com. 300 IN TXT "v=spf1 include:_netblocks.google.com ?all" google´s domain for sending mail is gmail.com. gmail.com is a virtual domain with no subdomains (afaik) and is mapped onto google, so if you check the senders no [email protected] could pass even using SPF or not. as you said, if you dig: dig -t txt gmail.com ;; ANSWER SECTION: gmail.com. 244 IN TXT "v=spf1 redirect=_spf.google.com" dig -t txt _spf.google.com ;; ANSWER SECTION: _spf.google.com. 300 IN TXT "v=spf1 include:_netblocks.google.com ?all" if you dig a bit more: dig -t txt www.google.com you get no answer because there is not SPF record for www.google.com, so you can forge emails as if they come from www.google.com even if there exists an SPF record for google.com !