Yes, I always use a task to send email for exactly this reason. Easily solved, but really kind of silly.
On Sep 10, 2011, at 5:16 PM, JH wrote: > This error was happening a year ago when I used to send gae email. I > get far less urlfetch timeouts when sending via Amazon... If you are > going to email with gae you need to do it via tasks so they will > retry. You will continue to see this mail.send timeout. > > On Sep 10, 2:46 pm, Joshua Smith <[email protected]> wrote: >> On Sep 10, 2011, at 2:18 PM, Robert Kluin wrote: >> >>> Email is basically asynchronous. >> >> And yet the most common timeout error I see in my apps is: >> >> DeadlineExceededError: The API call mail.Send() took too long to respond and >> was cancelled. >> >> I know this is a totally different kind of synchronous than you were talking >> about, but it's ironic, no? If there's one thing a distributed system >> should be able to do with no delay, it's sending email. >> >> -Joshua > > -- > 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. > -- 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.
