any follow up on this? 12mb attachments are not uncommon

I need to set the lambda memory limit up to 1GB in order to process 24MB attachments. Any update?

@drabaioli no this project has been pretty silent since it's release. If you really want to use this I'd brush up on the underlying technologies and make the improvements you need yourself.

I found a possible alternative (I haven't tried that yet though) : https://github.com/tedder/aws_lambda_ses_forwarder_python3/blob/master/lambda-ses-forwarder-py3.py

I myself ended up paying for email (zoho) because I don’t want to worry about not receiving an email and don’t have time to learn ses and serverless

AWS SES has a limit of 10 MB on message size that can be sent. This includes all attachments after encoding, so it effectively limits binary files to around 7.5 MB.

See: https://docs.aws.amazon.com/ses/latest/DeveloperGuide/limits.html

When the message size is too large, I see this error message in the Cloudwatch Logs:

sendRawEmail() returned error.
error: 
{ InvalidParameterValue: Message length is more than 10485760 bytes long: '10515066'.
at Request.extractError (/var/runtime/node_modules/aws-sdk/lib/protocol/query.js:47:29)
...

In my testing, this module handled a message with a 7.4 MB binary attachment (before encoding) with 768 MB memory configuration in Lambda and a 6 MB binary attachment (before encoding) with 512 MB memory configuration. I used the Node.js 8.10 runtime with a 30 second timeout.

Thanks @arithmetric , I clearly see the limits set by AWS SES. Nonetheless I'm able to forward emails of 24MB. Only problem is that the memory required by the lambda function is over 1GB.
I wonder if it's possible to reduce the amount of memory used by the JS handler.