- Newest
- Most votes
- Most comments
Hi,
No, WorkMail has no option to limit the size of inbound mail. There are options to achieve this, one of which is the suggestion re:Post Agent of using Mail Manger. Do note that using Mail Manager will bring extra costs.
An alternative solution is to run a synchronous lambda on the WorkMail side where it can check the message size using the WorkMail Message flow https://docs.aws.amazon.com/workmail/latest/adminguide/lambda-content.html and https://docs.aws.amazon.com/workmail/latest/APIReference/API_Operations_Amazon_WorkMail_Message_Flow.html
Kind regards, Robin
Yes, you can set a lower maximum email size limit in Amazon SES using Mail Manager's traffic policies. When creating a traffic policy through the CreateTrafficPolicy API, you can specify the MaxMessageSizeBytes parameter, which allows you to set a custom maximum message size. Any email exceeding this size will be blocked. The parameter accepts integer values with a minimum of 1 byte.
It's worth noting that while Amazon SES has default maximum message size limits (10 MB for SES v1 API and 40 MB for SES v2 API or SMTP), you can use traffic policies to implement a more restrictive size limit like your desired 250-500 KB.
Additionally, if you're using Amazon SNS as part of your email receiving workflow, be aware that there's a built-in 150 KB size limit for emails published to SNS topics. Emails larger than this will bounce, regardless of your other settings.
For S3 actions in receipt rules, the maximum email size is 40 MB, but your custom traffic policy would take effect before this limit is applied if you set a lower threshold.
Sources
Amazon SES inbound message could not be delivered | AWS re:Post
CreateTrafficPolicy - Amazon SES Mail Manager API
S3Action - Amazon Simple Email Service
answered a year ago
Relevant content
asked 3 years ago
asked 5 years ago
asked 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 7 months ago

Thanks for your suggestion. From what I can see on AWS Lambda pricing page, you get 1 million requests and 400,000 GB-s for free per month. Which would basically mean that even if I add a filter with lambda, it will still be technically free, and get the desired outcome with only the price of WorkMail. Am I right about that?