-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Frank Ellermann wrote:
I think [Google] reject FAIL, [...]
See also <http://www.openspf.org/Frank_Ellermann/Google>, if it's
generally interesting I could move it to an "ordinary" openspf page.
Before we consider that, how can we be sure that the rejection demons-
trated on that page is actually due to an SPF Fail?
| Apparently Gmail rejects SPF FAIL after DATA:
|
| 20071104 21:21:55 TCP connection with GMAIL-SMTP-IN.L.GOOGLE.COM:25
| 21:55.97 220 mx.google.com ESMTP y37si6730238iky
| 21:55.97 ehlo xyzzy.dnsalias.org
| 21:56.12 250-mx.google.com at your service, [62.134.88.223]
| [...]
| 21:56.12 mail from:<nobody(_at_)xyzzy(_dot_)claranet(_dot_)de>
| 21:56.26 250 2.1.0 OK
| 21:56.26 rcpt to:<hmdmhdfmhdjmzdtjmzdtzktdkztdjz(_at_)gmail(_dot_)com>
| 21:59.88 250 2.1.5 OK
| 21:59.88 data
| 21:59.99 354 Go ahead
| 22:00.29 .
| 22:01.99 550-5.7.1 [62.134.88.223] The IP you're using to send email is not
authorized
| 22:01.99 550-5.7.1 to send email directly to our servers. Please use
| 22:01.99 550 5.7.1 the SMTP relay at your service provider instead. [...]
Yes, their SMTP and DSN status codes match what RFC 4408 recommends for
rejections due to SPF Fail, but I looked into the definitions of these
status codes and it's very well possible that they and the SMTP response
text are due to some other IP-based policy (e.g., a dynamic IP address
blacklist).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHbXz9wL7PKlBZWjsRAmVoAJ9Xjobj8Ii03R0Gcyk74/J92+rIYwCeOZgR
uOkSshCcoPx23jDFVsbKIm4=
=URAP
-----END PGP SIGNATURE-----
-------------------------------------------
Sender Policy Framework: http://www.openspf.org
Archives: http://v2.listbox.com/member/archive/735/=now
RSS Feed: http://v2.listbox.com/member/archive/rss/735/
Modify Your Subscription:
http://v2.listbox.com/member/?member_id=2183229&id_secret=78857552-af036f
Powered by Listbox: http://www.listbox.com