[google-appengine] Comcast not accepting outgoing emails

[emu...@conceptuamath.com]

I have a domain registered on Godaddy, and added to Google Apps.
Through Google Apps, i added my AppEngine application as service.
I"ve setup the DNS records to server www from Appengine, this works
well. I've added the SPF record to my DNS records on Godaddy based on
this article: http://www.google.com/support/a/bin/answer.py?answer=178723.
My app serves correctly off the domain. Everything works well except
that the emails I send with the registration activation never arrive
to SOME recipients. They successfully arrive to many recipients
(gmail, yahoo and others), but NEVER arrive to comcast.net accounts
and some others. Any help would be appreciated.

--
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.

[Mabuse]

Hello,
I've the same issue. The german mail provider web.de rejects all mails
from the app engine.
It seems there is a syntax error in the mail header. See:
http://code.google.com/p/googleappengine/issues/detail?id=1800#c15
It's an blocker for serious apps with GAE.

[Jody Belka]

There is indeed a serious. Google is including an _ as part of a dns label in (I assume) the return path. An _ is not valid as part of a dns label. The only valid things are letters, numbers, and a dash (-). This is something that Google should urgently fix, as any servers that check the return path for validity will reject mail.

[emu...@conceptuamath.com]

Yes, I think that is my issue. Here is the return header from an
email that was successfully received by yahoo:

Return-Path: <34vdlsw0jb-ooazoqbfgmymftsymux.oayqygdygdkmtaa.oay@1rf-
h_fbpz96xcrx.apphosting.bounces.google.com>

note: @1rf-h_fbpz96xcrx.

The underscore is illegal. I think that is why many hosts are
rejecting my emails. The receiver is never notified in any way.

On Apr 19, 9:12 am, Jody Belka <j...@jj79.org> wrote:
> There is indeed a serious. Google is including an _ as part of a dns
> label in (I assume) the return path. An _ is not valid as part of a
> dns label. The only valid things are letters, numbers, and a dash (-).
> This is something that Google should urgently fix, as any servers that
> check the return path for validity will reject mail.
>

> On 19 April 2010 15:38, Mabuse <stefan.urban...@web.de> wrote:
>
>
>
>
>
> > Hello,
> > I've the same issue. The german mail provider web.de rejects all mails
> > from the app engine.
> > It seems there is a syntax error in the mail header. See:
> >http://code.google.com/p/googleappengine/issues/detail?id=1800#c15
> > It's an blocker for serious apps with GAE.
>
> > --
> > 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<google-appengine%2Bunsubscrib e...@googlegroups.com>
> > .

> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.
>
> --
> 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 athttp://groups.google.com/group/google-appengine?hl=en.

[emu...@conceptuamath.com]

I've added a separate issue for the fact that the reply-address has an
illegal character that causes some email host to reject the email. it
issue number 3114. Please Star this issue and add a comment so it
get's attention.

Ed

On Apr 19, 9:12 am, Jody Belka <j...@jj79.org> wrote:

> There is indeed a serious. Google is including an _ as part of a dns
> label in (I assume) the return path. An _ is not valid as part of a
> dns label. The only valid things are letters, numbers, and a dash (-).
> This is something that Google should urgently fix, as any servers that
> check the return path for validity will reject mail.
>

> On 19 April 2010 15:38, Mabuse <stefan.urban...@web.de> wrote:
>
>
>
>
>
> > Hello,
> > I've the same issue. The german mail provider web.de rejects all mails
> > from the app engine.
> > It seems there is a syntax error in the mail header. See:
> >http://code.google.com/p/googleappengine/issues/detail?id=1800#c15
> > It's an blocker for serious apps with GAE.
>
> > --
> > 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<google-appengine%2Bunsubscrib e...@googlegroups.com>
> > .

> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.
>
> --
> 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 athttp://groups.google.com/group/google-appengine?hl=en.

[Jeff Schnitzer]

A link always helps:

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

Jeff

[emu...@conceptuamath.com]

I have resolved my problem with comcast.net and other hosts. It was
NOT the underscore issue. It was (you guessed it) my SPF record. The
_correct_ SPF entry for AppEngine apps that use a custom domain and
send mail is;

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

There are a number of discussions in this group that point to a Google
Apps Admin Help page that shows SPF entry that looks like this:
v=spf1 include:_spf.google.com ~all

That is NOT a correct entry. When I removed that entry and added the
one above, the issue resolved itself. If found the correct entry by
examining tweetdeck.com's DNS records. The are heavy users on
AppEngine's mail service, so I figured that they would have it right,
and they did. Thank you tweetdeck.

The underscore issue is still a real issue, but is was not my issue.



On Apr 19, 11:05 am, "emur...@conceptuamath.com"