the s~ is affecting what email address I can send email from. I am now forced to use no-reply@s~APP-ID.appspotmail.com
which as far as I know is not an RFC valid email address On Jan 24, 3:21 pm, "Ikai Lan (Google)" <[email protected]> wrote: > Yes, that is the goal. The s~ should not appear anywhere with the exception > of maybe the admin-console. If it's required anywhere else, that is a bug we > should address. > > -- > Ikai Lan > Developer Programs Engineer, Google App Engine > Blogger:http://googleappengine.blogspot.com > Reddit:http://www.reddit.com/r/appengine > Twitter:http://twitter.com/app_engine > > On Mon, Jan 24, 2011 at 2:12 AM, Waldemar Kornewald > <[email protected]>wrote: > > > Will this be fixed, so it's transparent? From an end-user point of view > > there is no reason to have such a distinction. It only complicates > > everything and people are sending me bug reports about the remote API not > > working with Django-nonrel when they use the high-replication datastore. In > > case the s~ prefix will stay, how can I detect this in Django-nonrel if I > > only know the normal appid and the user doesn't manually specify that his > > app uses the HR datastore? > > > Bye, > > Waldemar > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<google-appengine%[email protected]> > > . > > 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
