Are you calling the mail api directly or from the task queue? Even when I was using the mail api, I always sent mail by enqueueing a task (usually in a transaction). Timeouts are never an issue that way.
Jeff On Tue, Apr 5, 2016 at 1:36 PM, Chad Vincent <ccrvinc...@gmail.com> wrote: > I'm going to sit in the middle here. We have had several issues with spam > filters (including one yesterday), the "from" address is masked for bounce > purposes, so our IT staff always spends half an hour trying to figure out > why a notice got caught before they remember to search for "*. > apphosting.bounces.google.com" instead of "nore...@appid.appspotmail.com" > as the sender. > > On the flip side it's nice that we don't have to mess with storing > credentials for SendGrid, worrying about delay from the trip outside > causing timeouts (a lot of our outbound mail is process-intensive and > occasionally hits the timeout just from waiting for external data that I > need to start caching...), etc. > > So ultimately, I like having the mail API just because I don't have to > change anything and can put the rare issue off on a different department. > But I can see where it could be lacking for anyone less staffed or higher > volume than us. > > > On Monday, April 4, 2016 at 6:02:09 PM UTC-5, Anastasios Hatzis wrote: >> >> I agree with you PK. Using Mail API was easy to achieve and never had >> trouble with spam filters or anything (unlike with other services). Would >> be great if the quotas would be increased significantly, so we could use it >> for more than confirmation emails. >> >> I understand, there are services providing more features (in exchange for >> another billing account, credit card exposure, and money), and it's great >> to have options available. But in my opinion Mail API is great for what it >> is, it just needs higher (paid) quota. >> >> On Monday, April 4, 2016 at 11:29:31 PM UTC+2, PK wrote: >>> >>> I want to state that I disagree with Jeff. Whoever maintains the mail >>> service is doing a great job and something very useful. Just for the >>> record... >>> >>> Thanks, >>> PK >>> p...@gae123.com >>> >>> >>> On Apr 4, 2016, at 2:00 PM, Jeff Schnitzer <je...@infohazard.org> wrote: >>> >>> My only concern is getting the Mail API turned off as soon as possible >>> so whoever is working on it can go do something more useful :-) >>> >>> Jeff >>> >>> On Mon, Apr 4, 2016 at 8:37 AM, Nick (Cloud Platform Support) < >>> pay...@google.com> wrote: >>> >>>> Hey Jeff, >>>> >>>> While in this case, failure of sending was coming from an unexpected >>>> direction, prompting engineering action to fix the issue, and leading to >>>> our recommendations to run test emails before any campaigns, there does >>>> exist a bounce notification feature >>>> <https://cloud.google.com/appengine/docs/python/mail/bounce> which can >>>> be used to detect the most common email failures. I hope this helps ease >>>> your concerns. >>>> >>>> Best wishes, >>>> >>>> Nick >>>> Cloud Platform Community Support >>>> >>>> On Sunday, April 3, 2016 at 12:04:12 PM UTC-4, Jeff Schnitzer wrote: >>>>> >>>>> On Mon, Mar 28, 2016 at 8:24 AM, Rob Williams <r...@workshoptwelve.com >>>>> > wrote: >>>>> >>>>>> >>>>>> The App Engine Mail API is fully featured and fully documented. >>>>>> >>>>> >>>>> >>>>> I hate hearing people say things like this. The _bare minimum_ >>>>> expected of a service that delivers email is some tracking of whether or >>>>> not that email was delivered. If you actually care about whether your >>>>> customers receive the email you are sending, you should not be using the >>>>> App Engine Mail API. It is not “fully featured”. >>>>> >>>>> Jeff >>>>> >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Google App Engine" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to google-appengine+unsubscr...@googlegroups.com. >>> To post to this group, send email to google-a...@googlegroups.com. >>> Visit this group at https://groups.google.com/group/google-appengine. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/google-appengine/CADK-0ugPR63z9OgLShEtYqqz7OOBNxB5Ya4C6BpmdeHdtQ2v6g%40mail.gmail.com >>> <https://groups.google.com/d/msgid/google-appengine/CADK-0ugPR63z9OgLShEtYqqz7OOBNxB5Ya4C6BpmdeHdtQ2v6g%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >>> >>> -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to google-appengine+unsubscr...@googlegroups.com. > To post to this group, send email to google-appengine@googlegroups.com. > Visit this group at https://groups.google.com/group/google-appengine. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-appengine/6684ca4d-40d7-4992-ac01-c20144a7c2e7%40googlegroups.com > <https://groups.google.com/d/msgid/google-appengine/6684ca4d-40d7-4992-ac01-c20144a7c2e7%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/CADK-0ui3bAMP3ujhYAXkzMzrtF935kjxKTj9_hu6UkgjmoQsjA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
