I should add that we also use a third-party email system. Ultimately it's no harder to make a REST call to an external service than to make a call to MailService, and many services offer a much more robust solution. GAE's mail system has silly limitations like the inability to send emails with inline (Content-ID) image attachments.
Just make sure that your 'unit of work' is the same as a single urlfetch. You wouldn't want to put 100 REST calls in a single task - imagine it failed at #50, then the whole task will retry and re-spam #1-#49. If your mail service does "send this message to these 100 people", great; otherwise stick to one-email-per-task. We do one-email-per-task. Jeff On Sun, Jul 8, 2012 at 8:57 AM, Richard Watson <[email protected]> wrote: > Offload both transactional and bulk email to a 3rd-party email specialist. > It's their core competence, and you're likely to be able to send bulk email > with one api call once your list is set up. If you have issues you'll have > better insight into what those are. You can get delivery and read reports, > and automatic remove-me-from-your-list handling. > > > On Sunday, July 8, 2012 5:27:04 PM UTC+2, Per wrote: >> >> Hi Vik, >> >> technical details aside, keep in mind that the spam filter settings on App >> Engine can be pretty strict. We have been sending mails for 18 months now, >> increasing the number gradually, and we also used DKIM signing. Still, >> suddenly some time last week our mails stopped getting sent. From all I can >> tell some Google mechanism decided that we're a spammer. We have inquired >> with Google instantly, but of course the GAE customer service is poor as >> always and never got back to us. So we switched to an external email >> provider now (mailgun, but there are dozens out there), and I'm quite happy >> with that, since tracking of emails is a lot more convenient too. It's not >> free though. >> >> Long story short, if you all of a sudden send 10k mails, be prepared to >> get filtered by Google because they think you're a spammer. Make sure to >> spread the load, and track what you have sent already, so you know what >> you'd need to resend if push comes to shove. >> >> Cheers, >> Per >> >> >> On Saturday, July 7, 2012 7:19:12 PM UTC+2, Vivek Kumar wrote: >>> >>> Hello >>> >>> We have around 10000 registered users with us who are blood donors. We >>> want to send them periodic emails like every month to remind them or their >>> account status etc. >>> Obviously, a single request cannot process so many emails. >>> >>> So, what is the suggested way to handle this use case without hitting >>> request time limits etc on app engine? >>> >>> our app is in GAE for java >>> >>> Vik > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/m4NlskwCrF8J. > > 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.
