Using this method is likely to get your SES account shut down

[orderamidchaos]

The Amazon SES sending for AWS account xxxxxxxxxxxxx, which lists you as a contact or owner, has been put on probation in AWS region US East (N. Virginia). You may still send mail with this account, but if you do not fully address the problem(s) listed, you will lose your ability to send with SES at the end of the probation period.

---

DETAILS

This problem is not due to bounces or complaints as measured directly by Amazon SES. Rather, a comprehensive human review of your account has found significant indicators that often lead to mailbox providers and/or anti-spam providers to classify your messages as unwanted sending. To protect our abuse detection process we do not provide specific information on the specific indications that have resulted in your account being flagged.

Some common factors that lead to this determination are messages being flagged by commercial spam filters, message content that implies the recipient has not explicitly requested the mail through an existing relationship with the sender, mismatches between the sending address and the branding within the message itself, content that does not make it obvious who the sending organization is, sending on a subject matter that is often associated with unwanted sending, formatting patterns often associated with unwanted sending, and sending from domains or linking to domains with a poor reputation with organizations that track online reputation. This represents some of the most common reasons, but is not to be interpreted as a comprehensive list.

[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.