# Configure direct-delivery incoming email for self-hosted sites with Mail-Receiver

**URL:** https://meta.discourse.org/t/configure-direct-delivery-incoming-email-for-self-hosted-sites-with-mail-receiver/49487
**Category:** Self-Hosting
**Tags:** email, how-to, advanced-setup, mail-receiver
**Created:** [August 31, 2016, 10:58am UTC](https://meta.discourse.org/t/configure-direct-delivery-incoming-email-for-self-hosted-sites-with-mail-receiver/49487 "2016-08-31T10:58:09Z")
**Posts on this page:** 1
**Showing post:** 544

<div class="post-metadata">

### Author: ![Simon\_Manning](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon_manning/32/198596_2.png) [@Simon\_Manning](https://meta.discourse.org/u/Simon_Manning)
#### Post date: [March 25, 2026, 11:43pm UTC](https://meta.discourse.org/t/configure-direct-delivery-incoming-email-for-self-hosted-sites-with-mail-receiver/49487/544 "2026-03-25T23:43:24Z")

</div>

I was referring to the `mail.domain.tld` A record being set to DNS Mode Only rather than the `forum.domain.tld` A record, however I realised that I have been misinterpreting how SMTP clients authenticate TLS certificates.

The behaviour I was seeing was an artefact of the default opportunistic method which does not validate the hostname, so my assertion that it validates the hostname of the MX record rather than the target of the MX record was incorrect. It would work in most cases but not if DANE or MTA-STS are used for enforcing TLS identity authentication.

---

_[View the full topic](https://meta.discourse.org/t/configure-direct-delivery-incoming-email-for-self-hosted-sites-with-mail-receiver/49487)._
