Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

SES 10MB Limits

0

This is NOT a LIMIT INCREASE question. Using SES we cannot receive e-mails with a total size > 10 MB. Amazon says the maximum RECEIVING (not Sending) size is 40MB. Amazon states that we need to upgrade to SES API V2, but we don't use API's to RECEIVE e-mails to SES. Rather, our SES account receives e-mails from Microsoft Exchange, GMail, Yahoo, Hotmail, etc., etc., etc., and nowhere ever have we been able to RECEIVE an e-mail to SES greater than 10MB. We've received over 100,000 e-mails to SES and none are over 10MB. For example, If we send a 15MB e-mail to SES it won't process it. We can prove this.

It is our position that SES cannot receive e-mails from the outside community (not V2 of their SDK) greater that 10MB. Please, if someone has any information that can assist we'd appreciate it. Currently Amazon wants us to upgrade our plan to pay for support when we feel their published documentation misrepresents their offerings.

Cheers!

Topics
Front-End Web & MobileBusiness Applications
Tags
Amazon Simple Email Service
Language
English
asked 3 years ago1.2K views
3 Answers
1
Accepted Answer

Hi,

You should be able to receive messages and store them in S3 buckets up to 40 MBs, regardless the sender and whether he uses SESv2 or not. This is mentioned here: https://docs.aws.amazon.com/ses/latest/dg/quotas.html#:~:text=Maximum%20email%20size%20(including%20headers)%20that%20can%20be%20stored,No

The fact that you cannot receive messages greater than 10MBs could have something to do with the sender and not the receiver. Of course this is not guaranteed or confirmed. To have a more concise answer, you will have to open a case with SES Premium Support, and explain what happens exactly. By the way, I've just tested that and it worked fine with me.

Hope this helps! Mo

answered 3 years ago
EXPERT
reviewed a year ago
0

Hi Mo.

Thank you for your response. After some additional testing, I agree with you that SES does receive the e-mail, but SES does something funky. When you're using an SNS trigger on an S3 bucket that SES dumps into and you send an e-mail to SES with a ~8+ MB attachment the Signature becomes to large for SNS to deliver. Interestingly, sending a 30MB e-mail directly to S3 (circumventing SES) works because for some reason the SNS Signature is much smaller. It seems that when SES receives an e-mail the SNS Signature is relative in size to the size of the S3 contents, but this is not the case when SES is not a part of the picture.

Cheers!

answered 3 years ago
0

Hi,

I am not sure that I do understand what you are doing correctly, so let me try to validate my understanding.

  1. You are using SES to receive messages and store them in S3 bucket.
  2. On the S3 side, you configured SNS topic to be triggered once an object is placed in the S3 bucket.
  3. This SNS topic is capable of generating a notification, when the message placed in the S3 is smaller than 10MBs. However it is not doing the same, when the message delivered to the S3 bucket is larger than 10MBs.

Did I get that right?

You also said, that the SNS notification works fine when you send a message to the S3 bucket without SES being involved in the equation. Did I get that right? If yes, how exactly do you send messages to S3 without SES being involved?

Thanks! Mo

answered 3 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content