ashanfernando / sesemailforward Goto Github PK

Emails are dropped if they are larger than 256kb. This is caused by SNS file size limitation

Hello Team,

Is the stack compatible with nodejs 10?

while preparing the stack, aws stops the process with an error saying that nodejs4.3 is no longer supported and you should upgrade to 8.1

exact error:

The runtime parameter of nodejs4.3 is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs8.10) while creating or updating functions. (Service: AWSLambdaInternal; Status Code: 400; Error Code: InvalidParameterValueException; Request ID: 5f164ac7-1e89-11e9-b1bc-e9d7c3aacfd1)

Could you add the SES steps to the CFn template? https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ses-receiptrule.html

I have SES fully set up, with verified email domain, DKIM Verification set up and Mail From successfully set up. The stack seems to have been built correctly, with FromAddress and ToAddress values saved. Additionally, I've built a Rule as instructed with the Recipient as a destination in my verified domain.

However, when emailing this Recipient, no forwarding is taking place and I see no log from the Lambda function in Cloudwatch. I'm at a loss to even begin to troubleshoot this, as I cannot find any SNS log files. Any ideas?

In order for me to use multiple from_address (e.g. to forward to the same address), do I need to re-deploy the entire stack?

How can I duplicate the lamdba function that was created?

This error appears when using with CF
The runtime parameter of nodejs8.10 is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs12.x) while creating or updating functions. (Service: AWSLambdaInternal; Status Code: 400; Error Code: InvalidParameterValueException; Request ID: 53f386dc-2f29-49c9-bd85-6cf080ff4ea2)

After creating the stack I get this error message in my CloudWatch Logs

TypeError: Cannot read property 'from' of undefined
at exports.handler (/var/task/index.js:14:55)

This is line 14:
headers += "Reply-To: "+msgInfo.mail.commonHeaders.from[0]+"\r\n";

Content-Type headers spanning multiple lines, like the ones uses by PGP/MIME, get torn apart.

For example the following excerpt of an email (last lines of header + start of body):

MIME-Version: 1.0
Content-Type: multipart/encrypted;
 protocol="application/pgp-encrypted";
 boundary="xRmQHxB0D5FgqSvOWFFhW9uLSlHPBbY4w"

This is an OpenPGP/MIME encrypted message (RFC 4880 and 3156)
--xRmQHxB0D5FgqSvOWFFhW9uLSlHPBbY4w
Content-Type: application/pgp-encrypted
Content-Description: PGP/MIME version identification

becomes this:

Subject: Fwd: Test
Content-Type: multipart/encrypted;
MIME-Version: 1.0

which then fails to be parsed correctly.

I guess the best solution would be to keep the existing headers and replace the relevant ones instead of re-writing them all