The challenging part of email sending is the verification and related dns uglinesses, so it's not as simple as replacing the API layer
Even setting up senders with App Engine is quite challenging, you have to create the email, add that email as an admin etc. (back in the old days, not sure how it works now, the hard part is the research and verification) My suggestion would be to take the hard path and do what sendgrid does, manually hunt the abusers Here is a funny analysis of the situation: 1) Google is in the cloud provider business, Google wants people to use it's cloud offerings 2) Google shuts down a cloud service, Google sends precious customers to another company It's admirable how contradicting (1) + (2) is I think the contradiction arises from (1) - Why is Google providing cloud services? Maybe it shouldn't, if it's pulling out of the Mail, the same could happen for all of the services soon I think this is why this situation is concerning Other than this, I roughly agree with how easy it would be to move the mail sending elsewhere, especially for apps that send small amount of emails, for >1000 emails, I don't think SendGrid would easily allow sending emails, as far as I contacted such services before, they considered high amount of emails as newsletters and required very strict consents from users and proof of such consent I would probably move to AWS's email service, I have been using it on SDK for maybe ~5+ years, same code still works for free -- 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/eee70341-7bc2-40ac-8b2e-24f4469da3ed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
