SPF Records for App Engine?

[Dave Peck]

My sign-up validation emails are ending up in users' junk mail
folders.

What's the scoop with SPF records for App Engine? I found a few older
posts on this group about it, but nothing from a GOOG employee or
pointing to official GOOG documentation.

Could someone point me in the right direction here?

Thanks,
Dave

[Chris Copeland]

If you are sending from an address f...@yourdomain.com and yourdomain.com is setup with Google Apps, then here are the instructions:

http://www.google.com/support/a/bin/answer.py?answer=178723

If that doesn't help (Yahoo may still be a problem for you), then just use Postmark or Amazon.

-Chris

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

[Dave Peck]

I've seen some claims from potentially reliable sources that the
correct SPF record is in fact:

v=spf1 include:aspmx.googlemail.com ~all

But this seems wrong given the link you just pointed me to?

Thanks!

Cheers,
Dave

[Barry Hunter]

aspmx.googlemail.com is simply a redirect to _spf.google.com

# dig aspmx.googlemail.com TXT
;; ANSWER SECTION:
aspmx.googlemail.com. 4174 IN TXT "v=spf1
redirect=_spf.google.com"

I would think using _spf.google.com directly would be safer, but
shouldnt really matter.

We where once told to use _netblocks.google.com by a google employee
in this forum. It returns the same IP ranges as _spf anyway.

[Greg]

Hi Dave -

I implemented SPF records and they helped, but you're going to find
Yahoo Mail blocks your messages even with SPF. I've been fighting a
losing battle with them to whitelist my domain. They will only
whitelist an IP address, which means we're stuck because Appengine
uses many varying IP addresses.

Yahoo basically told me the only solution is to use DKIM. Google
recently implemented this for Google Apps mail, but not Appengine. We
need a small change to the Appengine mail API to add the DKIM header
ourselves - please star this issue if you think it might be useful for
you too:

http://code.google.com/p/googleappengine/issues/detail?id=3161

I'm not happy to switch mail to another provider because then I have
additional points of failure.

Cheers
Greg.