# Cannot send any email with AWS SES

**URL:** https://meta.discourse.org/t/cannot-send-any-email-with-aws-ses/147406
**Category:** Self-hosting
**Created:** [April 9, 2020, 11:26am UTC](https://meta.discourse.org/t/cannot-send-any-email-with-aws-ses/147406 "2020-04-09T11:26:58Z")
**Posts on this page:** 10
**Page:** 1

<div class="post-metadata">

### Author: ![Mustafa\_Demir](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mustafa_demir/32/176328_2.png) [@Mustafa\_Demir](https://meta.discourse.org/u/Mustafa_Demir)
#### Post date: [April 9, 2020, 11:26am UTC](https://meta.discourse.org/t/cannot-send-any-email-with-aws-ses/147406/1 "2020-04-09T11:26:58Z")

</div>

Hello, I’ve just installed Discourse on my Ubuntu server. It’s running on production and I can’t send any email from the Discourse. I created an IAM user on SES and entered my SES SMTP credentials correctly to Discourse’s config file. But I can’t get any emails from it. My SMTP works with telnet BTW. Can anyone help me to solve this problem? Thanks

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [April 9, 2020, 11:29am UTC](https://meta.discourse.org/t/cannot-send-any-email-with-aws-ses/147406/2 "2020-04-09T11:29:33Z")

</div>

The problem I assume is related to Your SES account not having limits. Check it’s sending limits, it may still be in sandbox mode and You may have to request AWS support to raise your sending limits.

---

<div class="post-metadata">

### Author: ![Mustafa\_Demir](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mustafa_demir/32/176328_2.png) [@Mustafa\_Demir](https://meta.discourse.org/u/Mustafa_Demir)
#### Post date: [April 9, 2020, 11:31am UTC](https://meta.discourse.org/t/cannot-send-any-email-with-aws-ses/147406/3 "2020-04-09T11:31:36Z")

</div>

I’ve just sent 60k emails a few days ago with Sendy and it worked well. It’s not in sandbox mode and my domain is verified and also I’m using SES on cloud functions too and it works fine as well. I don’t think that problem is related to the SES limits.

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [April 9, 2020, 11:32am UTC](https://meta.discourse.org/t/cannot-send-any-email-with-aws-ses/147406/4 "2020-04-09T11:32:50Z")

</div>

Is Your sending domain the same as Your discourse domain? E.g. if You’re sending from `discourse.example.com` then is the same verified at SES too?

---

<div class="post-metadata">

### Author: ![Mustafa\_Demir](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mustafa_demir/32/176328_2.png) [@Mustafa\_Demir](https://meta.discourse.org/u/Mustafa_Demir)
#### Post date: [April 9, 2020, 11:35am UTC](https://meta.discourse.org/t/cannot-send-any-email-with-aws-ses/147406/5 "2020-04-09T11:35:35Z")

</div>

My domains is `example.com` and the forum’s domain is `forum.exmaple.com`. I’m still waiting for approval for the subdomain but AWS says once you verified your domain, all your subdomains should work fine. But is this could be the problem? The subdomain’s status is `pending verification` ATM.

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [April 9, 2020, 11:37am UTC](https://meta.discourse.org/t/cannot-send-any-email-with-aws-ses/147406/6 "2020-04-09T11:37:40Z")

</div>

One workaround I can suggest is to change your notification email address in discourse.

You can use `noreply@example.com` instead of `noreply@forum.example.com` which should get your emails delivered.

You can maybe check if amazon wants you to create additional DNS TXT records for the subdomain modification.

---

<div class="post-metadata">

### Author: ![Mustafa\_Demir](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mustafa_demir/32/176328_2.png) [@Mustafa\_Demir](https://meta.discourse.org/u/Mustafa_Demir)
#### Post date: [April 9, 2020, 11:38am UTC](https://meta.discourse.org/t/cannot-send-any-email-with-aws-ses/147406/7 "2020-04-09T11:38:54Z")

</div>

> You can use `noreply@example.com` instead of `noreply@forum.example.com` which should get your emails delivered.

I tried to change it but couldn’t find anything on the internet. Do you know how to change it?

---

<div class="post-metadata">

### Author: ![Mustafa\_Demir](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mustafa_demir/32/176328_2.png) [@Mustafa\_Demir](https://meta.discourse.org/u/Mustafa_Demir)
#### Post date: [April 9, 2020, 11:41am UTC](https://meta.discourse.org/t/cannot-send-any-email-with-aws-ses/147406/8 "2020-04-09T11:41:36Z")

</div>

Yay! I changed the domain in the forum’s settings and it worked!  
Dude, Thank you so much for your fast reply and support! Thank you!

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [April 9, 2020, 11:41am UTC](https://meta.discourse.org/t/cannot-send-any-email-with-aws-ses/147406/9 "2020-04-09T11:41:44Z")

</div>

Look at the very end of Your app.yml file

There will be something like `sitesetting.notification_email`  
Uncomment that line then rebuild discourse. That should suffice.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [May 9, 2020, 11:41am UTC](https://meta.discourse.org/t/cannot-send-any-email-with-aws-ses/147406/10 "2020-05-09T11:41:48Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
