Hi everyone,

We know that almost every developer has a need to send email and that the
GAE Mail API hasn't been given the love it deservers. I am trying to make
it better for everyone on Google Cloud. Please feel free to email me
directly with your requirements and a bit more about your use cases.

On Fri, Mar 31, 2017 at 7:44 AM, Kaan Soral <kaanso...@gmail.com> wrote:

> I don't know whether I missed it, but we never learned why "exactly" Mail
> was deprecated
>
> I wonder whether it was from a conflict of interest too, for example, it
> bothered me that my emails were marked as "Promotional", while they were
> actually "Social", in Gmail
>
> Anyway, that's why I also added the part about "investing some effort", as
> you pointed out, there are things that can be improved
>
> Fyi, I would love a metric based quota too, similar to AWS's solution to
> the issue, could even be more aggressive
>
> On Friday, March 31, 2017 at 5:38:16 PM UTC+3, Jeff Schnitzer wrote:
>>
>> How do you know that 80% of your emails sent with Google weren’t wasted?
>> GAE never provided deliverability statistics of any sort.
>>
>> On Fri, Mar 31, 2017 at 7:35 AM, Kaan Soral <kaan...@gmail.com> wrote:
>>
>>> I'm with Luca here
>>>
>>> Using external services introduces new points of failures and introduces
>>> new, edge complications that only arise when you get into things
>>>
>>> For example, on 10/18/16 I replied to this issue, afterwards, after the
>>> mourning period, I ended up using AWS, the email routine I used for GAE was
>>> too fast for AWS, I completely forgot about their throughput limitations,
>>> 80% of my emails were wasted, a bad start to the Halloween period
>>>
>>> On this thread, we end up repeating our views of the issue, however, to
>>> repeat my own view, I want GAE to be as independent as possible, instead of
>>> spawning, supporting other cloud services, why not provide all basic
>>> services in-house?
>>>
>>> For example, a Video/Live-Streaming solution from Google would be pretty
>>> good, I like Zencoder, yet integration was a challenge, it's tooo expensive
>>> for a startup
>>>
>>> Anyway, my point is, in-house is always better than external, survey us,
>>> ask us what we need, invest some effort into building new things, I'm sure
>>> Email will be on top of that list (I hope Video/Streaming is a runner-up,
>>> in the age that we live in, we really need affordable and agile video
>>> solutions too)
>>>
>>>
>>> On Friday, March 31, 2017 at 2:24:04 PM UTC+3, Bookingforce CTO wrote:
>>>>
>>>> Hello there,
>>>>
>>>>   being CTO of a company that is betting on Google Infrastructure when
>>>> I found out about the limitation to 100 recipients, at first I thought "ah,
>>>> I have to increase that quota", then, after asking (twice) to support team,
>>>> I felt like "what's wrong with GAE ?"
>>>>
>>>> The only fact that more than 100 emails is referred as "high volume" is
>>>> almost disturbing... we are using GAE to build cloud applications that
>>>> scale up using multiple instances but still we can't contact our customers
>>>> via email if they are more than 100 ? If you want to prevent spam, bill
>>>> each email, we may be willing to pay as much as we pay for other services.
>>>>
>>>> If you just don't want to offer a serious service about email, you
>>>> should think to discontinue the Mail API, like this it makes no sense.
>>>>
>>>> Cheers,
>>>>   Luca
>>>>
>>>> On Wednesday, October 26, 2016 at 7:49:05 PM UTC+2, Nick (Cloud
>>>> Platform Support) wrote:
>>>>>
>>>>> The Public Issue Tracker thread brought our attention has gotten
>>>>> tracked now, thanks to PK. We'll update it with any progress.
>>>>>
>>>>> Now, as much as I'm sure we all appreciate Jeff's kind offer, I don't
>>>>> think it will be necessary to pay him $1000, since Cloud Platform 
>>>>> Community
>>>>> Support are here to do a similar job at no cost. As said in other threads
>>>>> on this topic, if anybody at any time has issues migrating from any 
>>>>> service
>>>>> to any other, has questions about design patterns, has questions about the
>>>>> use of our APIs or how to refactor their code, etc., this forum is the
>>>>> perfect place for such higher-level discussion and we would be happy to
>>>>> discuss in depth.
>>>>>
>>>>> We never want users to feel left alone, and asking a question once has
>>>>> the benefit that all other users in a similar situation can read and learn
>>>>> from the thread. This doesn't fit under the umbrella of "platform issues /
>>>>> feature requests" (Public Issue Tracker) or "a specific error / stack
>>>>> trace" (Stack Overflow), so it would be fine to post such threads in this
>>>>> forum.
>>>>>
>>>>> As an additional, final comment, I'll say that we do pay close
>>>>> attention to the requests for services / service improvements that users
>>>>> bring forward, whether here or in the Public Issue Tracker. We've taken 
>>>>> the
>>>>> feedback from many users on the Mail API and bulk sending and while we
>>>>> don't promise any concrete action given this feedback, know that we have
>>>>> taken it into account and we want to thank you for bringing up how you 
>>>>> view
>>>>> things, what you'd like to see, etc.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Nick
>>>>> Cloud Platform Community Support
>>>>>
>>>>> On Tuesday, October 18, 2016 at 10:42:26 PM UTC-4, Jeff Schnitzer
>>>>> wrote:
>>>>>>
>>>>>> Since this thread keeps coming up… I’ll make you all an offer: For
>>>>>> $1k I’ll migrate your GAE app to Sendgrid, Mailgun, or whatever other 
>>>>>> email
>>>>>> service you want. Assuming your code isn’t spaghetti, it will probably 
>>>>>> take
>>>>>> me an hour. It should take you about the same or less.
>>>>>>
>>>>>> This is sooo much kvetching about something that is so trivial to fix.
>>>>>>
>>>>>> Jeff
>>>>>>
>>>>>> On Tue, Oct 18, 2016 at 9:27 AM, PK <p...@gae123.com> wrote:
>>>>>>
>>>>>>> +1 for Joshua’s comment.
>>>>>>>
>>>>>>> Nick, wrt "We always encourage users to make use of the Public Issue
>>>>>>> Tracker “ the issue is issue 10560
>>>>>>> <https://code.google.com/p/googleappengine/issues/detail?id=10560> stuck
>>>>>>> in state “New” for 2.5 years like 100s maybe thousands other issues in 
>>>>>>> the
>>>>>>> public tracker.
>>>>>>>
>>>>>>> PK
>>>>>>> p...@gae123.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Oct 18, 2016, at 8:50 AM, Joshua Smith <mrjoshu...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Nick,
>>>>>>>
>>>>>>> I know you are stuck in the apologist position, and there’s nothing
>>>>>>> you can do about it, but come on…
>>>>>>>
>>>>>>> It is positively absurd that GAE doesn’t include any bulk email
>>>>>>> capability. If you guys are concerned about spammers abusing the 
>>>>>>> service,
>>>>>>> just charge a penny per email sent or something.
>>>>>>>
>>>>>>> If it’s because google can’t figure out how to provide a reliable
>>>>>>> email service, maybe call the team over at gmail, I hear they have some
>>>>>>> experience in this area.
>>>>>>>
>>>>>>> You will never convince GAE users that having to use a third-party
>>>>>>> to send email is anything but a pathetic hack.
>>>>>>>
>>>>>>> -Joshua
>>>>>>>
>>>>>>> On Oct 18, 2016, at 10:55 AM, 'Nick (Cloud Platform Support)' via
>>>>>>> Google App Engine <google-a...@googlegroups.com> wrote:
>>>>>>>
>>>>>>> Hey PK and Kaan,
>>>>>>>
>>>>>>> I hear your concerns. I hope that I can moderate worries by saying
>>>>>>> the following in regard to each of the points you brought up:
>>>>>>>
>>>>>>> *1. Avoid paying for attachment bits through front-end*
>>>>>>>
>>>>>>> While the GCS integration to Mail API attachments will be discussed
>>>>>>> in the next point, there's another GCS solution here which is very 
>>>>>>> useful.
>>>>>>> You can generate URLs to the attachment objects and merely embed these 
>>>>>>> URLs
>>>>>>> in the email. This ultimately has the same transfer cost for the user's
>>>>>>> machine as downloading from a mail server storing the attachment, but is
>>>>>>> slightly different since you can recall the object at a later date.
>>>>>>>
>>>>>>> *2. Feature requests for GCS integration to Mail API*
>>>>>>>
>>>>>>> We always encourage users to make use of the Public Issue Tracker
>>>>>>> <https://code.google.com/p/googleappengine/issues/list> to make any
>>>>>>> feature requests that they think of. We track them and consider them, 
>>>>>>> and
>>>>>>> this is the best way to ensure that we know about it in a formal manner
>>>>>>> rather than just posting in a discussion thread. We look forward to all
>>>>>>> feature requests because it means users are working on the platform and
>>>>>>>
>>>>>>>
>>>>>>> *3. Platform Unity*
>>>>>>> We definitely recognize that the power of the platform comes from
>>>>>>> its unity and internal organization. The various services combine to 
>>>>>>> create
>>>>>>> an ecosystem where development can rapidly integrate many capabilities 
>>>>>>> to
>>>>>>> produce powerful apps. Because we understand that developers depend on 
>>>>>>> the
>>>>>>> services for app performance, we offer a minimum 1 year announcement 
>>>>>>> before
>>>>>>> deprecation, as you can read in the Cloud Platform Terms of Service
>>>>>>> <https://cloud.google.com/terms/>.
>>>>>>>
>>>>>>> We also do our best during any deprecation period to provide support
>>>>>>> and migration advice to developers. Community Support is a resource for 
>>>>>>> you
>>>>>>> developers, so please don't hesitate to ask us any questions or open
>>>>>>> discussions of architecture, design, etc. We can't prevent the web or 
>>>>>>> our
>>>>>>> services from changing over time, as all things must, but we can do our
>>>>>>> best to provide comprehensive support for users during these changes.
>>>>>>>
>>>>>>> For the moment, everything said above and elsewhere about the Mail
>>>>>>> API and Sendgrid remains good advice. Sendgrid is simply far better 
>>>>>>> suited
>>>>>>> to bulk messages, while the Mail API can be used effectively for
>>>>>>> administrative emails such as a password reset system, etc.
>>>>>>>
>>>>>>> As always, let us know your thoughts or if you have any further
>>>>>>> questions! We'll be happy to help.
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> Nick
>>>>>>> Cloud Platform Community Support
>>>>>>>
>>>>>>> On Monday, October 17, 2016 at 6:39:17 PM UTC-4, Kaan Soral wrote:
>>>>>>>>
>>>>>>>> Good thing we are locked-in for life to App Engine. Using App
>>>>>>>> Engine for maybe 6 years, It's part of me
>>>>>>>>
>>>>>>>> Seeing this announcement, and practically experiencing the
>>>>>>>> roadblock, devastates me
>>>>>>>>
>>>>>>>> The beauty of App Engine comes from it's unity, when you take a
>>>>>>>> vital part of that unity out and kill it, it inflicts terror and fear, 
>>>>>>>> I
>>>>>>>> fear that more and more services are going to be terminated one day
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> 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-appengi...@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/08c9a88a-
>>>>>>> 792e-45ee-89b9-426899c90900%40googlegroups.com
>>>>>>> <https://groups.google.com/d/msgid/google-appengine/08c9a88a-792e-45ee-89b9-426899c90900%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-appengi...@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/20F83DA1-
>>>>>>> 2445-4E7E-9359-C7E46DF4243A%40gmail.com
>>>>>>> <https://groups.google.com/d/msgid/google-appengine/20F83DA1-2445-4E7E-9359-C7E46DF4243A%40gmail.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-appengi...@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/CD897B33-
>>>>>>> 74C5-446A-BD38-02B3D817B889%40gae123.com
>>>>>>> <https://groups.google.com/d/msgid/google-appengine/CD897B33-74C5-446A-BD38-02B3D817B889%40gae123.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-appengi...@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/ms
>>> gid/google-appengine/dcb8c1f4-da05-49a1-ab8a-690809edb47d%
>>> 40googlegroups.com
>>> <https://groups.google.com/d/msgid/google-appengine/dcb8c1f4-da05-49a1-ab8a-690809edb47d%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 a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/google-appengine/p3tma8eFCM4/unsubscribe.
> To unsubscribe from this group and all its topics, 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/521bac1f-fcd7-47d1-9d42-
> ceebd9280c00%40googlegroups.com
> <https://groups.google.com/d/msgid/google-appengine/521bac1f-fcd7-47d1-9d42-ceebd9280c00%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Kim Lewandowski | Product Manager, Google Cloud Platform |
klewandow...@google.com

-- 
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/CAOkg9cpS0wkeFmtbkbPvAjyaBatfqtfx5Fazx671TXvS3A387A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to