Hey Emanuele,

I understand your concerns about needing to revise your codebase - nobody 
wants to spend more time than they need on maintaining or adjusting a 
system when they could be blazing new trails and writing new behaviour and 
system, but rest assured that we really do try to ensure that deprecations 
are announced well in advance of the final termination of a service, and we 
are committed to providing any migration help necessary. 

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!

Cheers,

Nick
Cloud Platform Community Support

On Tuesday, May 3, 2016 at 6:14:02 PM UTC-4, Emanuele Ziglioli wrote:
>
> yeah, one less reason to bet on App Engine: it's such a moving target.
> We can't afford to rewrite critical parts of the code every few years just 
> because APIs get deprecated.
> Blobstore first, now this.
> Mail has been the single most reliable feature for us over the past 5 
> years.
> I understand the problem and costs might be caused by those few spammers 
> who send millions of e-mails from GAE.
> Why don't you kick them out?
> Look at what the average user needs, and restrict the quota for cater for 
> us.
> Otherwise, just tell us what App Engine is and we'll figure out what to do 
> in the future.
> You keep telling us GAE's future is solid but then you strip it bits by 
> bits.
> Very frustrating.
>
> On Wednesday, 4 May 2016 05:21:37 UTC+12, John Wheeler wrote:
>>
>> The Mail API is extremely important to us and provides satisfactory 
>> deliverability for our use cases in its current form. For the amount of 
>> mail we send, alternatives are still too expensive. -1 on shutting the API 
>> down completely. We rely on it and find it useful.
>>
>> On Monday, May 2, 2016 at 1:43:21 PM UTC-7, Nick (Cloud Platform Support) 
>> wrote:
>>>
>>> Hey Joshua,
>>>
>>> That's certainly an interesting idea! While I can't guarantee we'll 
>>> implement it, be assured that we've heard this suggestion and will consider 
>>> it. In the meantime, if a deprecation were announced, we would certainly 
>>> welcome the opportunity to help as many users as possible easily migrate, 
>>> in whatever form that looks like.
>>>
>>> Cheers,
>>>
>>> Nick
>>> Cloud Platform Community Support 
>>>
>>> On Monday, May 2, 2016 at 11:35:35 AM UTC-4, Joshua Smith wrote:
>>>>
>>>> Suggestion for the team: If you do decide to do this, keep your 
>>>> existing API and just swap in SendGrid as the underlying transport layer. 
>>>> Maybe we could put our SendGrid API key (or however they deal with that) 
>>>> into the console, or in app.yaml someplace, or something like that.
>>>>
>>>> I’ve got dozens of apps on GAE, and do not relish the idea of porting 
>>>> them all to a different mail API. Especially since 99% of the mail sent is 
>>>> just error logging reports sent to me.
>>>>
>>>> -Joshua
>>>>
>>>> On Apr 29, 2016, at 3:27 PM, 'Nick (Cloud Platform Support)' via Google 
>>>> App Engine <[email protected]> wrote:
>>>>
>>>> Hey pdknsk,
>>>>
>>>> While I can't speak on any concrete plan to deprecate, the excellent 
>>>> quality of SendGrid (even at the free tier), combined with our 
>>>> 1-year-minimum deprecation policy timeline, should reassure everyone that 
>>>> there's nothing significant to worry about. If this were to occur, you can 
>>>> rest assured as well that we'd be happy to provide migration advice to 
>>>> anybody needing it during the deprecation. 
>>>>
>>>> Cheers!
>>>>
>>>> Nick
>>>> Cloud Platform Community Support
>>>>
>>>> On Friday, April 29, 2016 at 10:17:03 AM UTC-4, pdknsk wrote:
>>>>>
>>>>> https://cloud.google.com/appengine/docs/python/release-notes
>>>>>
>>>>> > Google no longer accepts quota increase requests for the mail 
>>>>> service. Customers should use Sendgrid instead.
>>>>>
>>>>> Google will probably deprecate it soon, and close it a year later.
>>>>>
>>>>
>>>> -- 
>>>> 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/6a7d9927-1924-4c87-94bc-115f0f7503d1%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/google-appengine/6a7d9927-1924-4c87-94bc-115f0f7503d1%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 [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/7539d22c-d9aa-4c06-8dde-e571e962ffb3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to