Using this method is likely to get your SES account shut down about aws-lambda-ses-forwarder

[3boysdad]

Care to share what you were doing? I've used this library for years and never got this, even when some Chinese spammer starting using my SES forwarding for 1000's of emails (block the IPs was the solution) per minute.

[tylerwalts]

I had a similar experience last year and then after I updated the lambda to drop emails that had spam scores set, my SES send rate dropped and I responded to AWS support with a screenshot of that metric which satisfied the concern and my account was set back to normal status. Similarly after I added more domains I then needed to request a SES rate limit increase by explaining my use case, and they gave it to me so that I would not get throttled.

[3boysdad]

@tylerwalts - interested in how you determine the SPAM scores? got a change to the code you can share?

[christoph-kluge]

@3boysdad you could check the SES verdict-objects. This is how I am dealing with it and dropping them.

https://docs.aws.amazon.com/ses/latest/DeveloperGuide/receiving-email-notifications-contents.html#receiving-email-notifications-contents-spamverdict-object

Also in my case I never received such a message from AWS (I'm running a saas-business with email forwarding support)

[3boysdad]

@christoph-kluge thanks, i'll take a look at this.