Thanks. I restructured my modules to put the mail handlers on the default
module. It would certainly be a useful feature to allow the incoming mail
handler to be on the non-default module.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
Indeed, looks like an excellent FR -- could you please enter it at
https://code.google.com/p/googleappengine/issues/list?can=2=Type%3DFeature
? (PK's FR about implicit use of GCS is also good, but I can see the
technical difficulties with that one in receiving emails, risking a DOS
attack by
Hi Alex,
one should be able to set quotas in the GCS bucket where attachments will be
temporarily stored. Therefore, I am not sure I see the DOS implications and why
they are any worse than today’s situation.
It is not really simple but this is where GCP & GAE can show leadership and
help
Unfortunately not much leadership to show. What you are looking for is
fully supported on AWS by storing / filtering inbound email directly to S3
buckets etc etc.
I won't copy the link, but you can read their blogpost of 28 SEP 2015.
I'm not affiliated with AWS - just a happy customer using
Not super familiar with modules, but what about using the default module to
store the mail and kick a task/URL on the handler module with the data?
On Tuesday, December 8, 2015 at 9:21:30 AM UTC-6, Phil Hodey wrote:
>
> I want to use the inbound email facility in GAE but need to have a
>
I have been doing what Nick suggests but have run into the following.
A use case I have run into is receiving e-mails with big attachments when my
default module has 128MB instances. the big attachments cause the instances to
crash. I cannot afford bigger instances and after all messages with
