How simple and easy life seems when one’s job is just to write support e-mails. Programming e-mail support in the cloud is a different story.
It took me a long time to get the GAE mail service work reliably and I am very happy with it. I had to deal with encoding issues, MIME issues, etc. I do not want to open this can of worms with another vendor’s APIs. Please do not change it/deprecate it except to improve it along the lines of improvements we have filed in the public tracker. Thanks, PK [email protected] > On May 4, 2016, at 10:10 AM, 'Nick (Cloud Platform Support)' via Google App > Engine <[email protected]> wrote: > > In this case, the migration from Mail API to a similar mail API elsewhere on > the net is mostly a very linear code change - merely take the same parameters > (recipients, from, subject, body, attachments) and provide them to the other > API. For more advanced mail features, you can work with the documentation of > whichever other mail provider you choose to determine how to do whatever it > is you want. If you would like, you could open a thread to explicitly ask the > community to assist with advice on how to adjust anything that you might find > to be particularly difficult. We're here to help, not just Googlers but the > community of developers in general! -- 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 [email protected]. To post to this group, send email to [email protected]. 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/0BDF3DC1-F190-4D8E-BD22-AB8D17F7C090%40gae123.com. For more options, visit https://groups.google.com/d/optout.
