# Discourse and Amazon SES - not ready?

**URL:** https://meta.discourse.org/t/discourse-and-amazon-ses-not-ready/201683
**Category:** Support
**Created:** [August 25, 2021, 1:59pm UTC](https://meta.discourse.org/t/discourse-and-amazon-ses-not-ready/201683 "2021-08-25T13:59:30Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![wlandgraf](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/wlandgraf/32/154660_2.png) [@wlandgraf](https://meta.discourse.org/u/wlandgraf)
#### Post date: [August 25, 2021, 1:59pm UTC](https://meta.discourse.org/t/discourse-and-amazon-ses-not-ready/201683/1 "2021-08-25T13:59:30Z")

</div>

Hi all,  
I’m having a hard time in getting Discourse properly configured with Amazon SES. I wonder if others are having the same issue?

I have asked questions in these other Discourse topics, [here](https://meta.discourse.org/t/bounced-e-mails-from-amazon-ses-sns-not-working/200209) and [here](https://meta.discourse.org/t/handling-bouncing-e-mails/45343/185), but got no answer so far.

First problem is that the handler of SNS notifications is not working. I [described the issue in this topic](https://meta.discourse.org/t/bounced-e-mails-from-amazon-ses-sns-not-working/200209) but I don’t have enough Ruby knowledge to solve it myself, although I know what’s going on.

Since SNS is not working, I had to enable e-mail forwarding in SES to send the bounce messages to discourse via VERP, but this is not desired as it keeps forwarding all the bounced e-mails from all other applications I use SES with, not only Discourse.

Ideally the SNS handler should be fixed. Any ideas? Is anyone properly handling SES bouncing with Discourse?