# Direct-delivery: incoming mail LetsEncrypt failure (prop.ltcmp.net.key is wrong) & nondelivery due to this?

**URL:** https://meta.discourse.org/t/direct-delivery-incoming-mail-letsencrypt-failure-prop-ltcmp-net-key-is-wrong-nondelivery-due-to-this/133525
**Category:** Self-hosting
**Tags:** email
**Created:** [15 november 2019 om 23:01 UTC](https://meta.discourse.org/t/direct-delivery-incoming-mail-letsencrypt-failure-prop-ltcmp-net-key-is-wrong-nondelivery-due-to-this/133525 "2019-11-15T23:01:14Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![mreach](https://avatars.discourse-cdn.com/v4/letter/m/9d8465/32.png) [@mreach](https://meta.discourse.org/u/mreach)
#### Post date: [16 november 2019 om 15:55 UTC](https://meta.discourse.org/t/direct-delivery-incoming-mail-letsencrypt-failure-prop-ltcmp-net-key-is-wrong-nondelivery-due-to-this/133525/2 "2019-11-16T15:55:35Z")

</div>

One thing I noticed, obviously, was that `/letsencrypt/domain.tld/prop.ltcmp.net.key` was missing from the contents of the folder:

```plaintext
discourse-mail-receiver:/# ls -tlrha letsencrypt/domain.tld
total 40
-rw-r--r-- 1 root root 3.2K Nov 10 05:10 domain.tld.key
-rw-r--r-- 1 root root 208 Nov 10 05:10 domain.tld.csr.conf
-rw-r--r-- 1 root root 1.6K Nov 10 05:10 domain.tld.csr
-rw-r--r-- 1 root root 2.2K Nov 10 05:10 domain.tld.cer
-rw-r--r-- 1 root root 3.8K Nov 10 05:10 fullchain.cer
-rw-r--r-- 1 root root 1.6K Nov 10 05:10 ca.cer
drwxr-xr-x 3 root root 4.0K Nov 10 05:10 .
-rw-r--r-- 1 root root 799 Nov 11 15:56 domain.tld.conf
drwxr-xr-x 2 root root 4.0K Nov 11 27 15:56 backup
drwxr-xr-x 8 root root 4.0K Nov 16 00:49 ..

```

It’s interesting since this goes back to [this question here](https://meta.discourse.org/t/straightforward-direct-delivery-incoming-mail/49487/195) by @surety that seems to have not received a direct answer.

The thread there seems to continue to discuss this point, but there’s so much chatter in that thread now that things can become confusing and thus why I’ve created a topic here (to achieve greater clarity for future users with such trouble).

It appears as though the `mail-receiver.yml` config’s entry `POSTCONF_smtpd_tls_key_file`’s value of `/letsencrypt/domain.tld/prop.ltcmp.net.key ` must be replaced with `/letsencrypt/domain.tld/domain.tld.key`.

So the answer to @surety’s #1 question is “YES” this is correct to replace this entry’s contents with the one that you see. #2 also seems correct to leave as default.

I believe that perhaps either @pfaffman or @mpalmer probably should retool the container creation script to have the correct .key file instead of this (apparent wrong) `prop.ltcmp.net.key` entry…

At this point I am now fortunately able to move on from and past @mpalmer’s step:

> You can also now try sending an e-mail to `nobody@forum.example.com` . While Discourse won’t do anything _useful_ with it yet, the e-mail you sent should show up in your admin panel under “Emails”, “Rejected” in a matter of seconds. If that happens, you’re _definitely_ ready to proceed.

Since now my test email is showing up in the Discourse `/admin/email/rejected` list! 🙂

---

_[View the full topic](https://meta.discourse.org/t/direct-delivery-incoming-mail-letsencrypt-failure-prop-ltcmp-net-key-is-wrong-nondelivery-due-to-this/133525)._