# Does DISCOURSE\_SMTP\_ADDRESS do MX lookup

**URL:** <https://meta.discourse.org/t/does-discourse-smtp-address-do-mx-lookup/37839>\
**Category:** Product Support\
**Created:** [12 בינואר,‏ 2016,‏ 4:28pm UTC](https://meta.discourse.org/t/does-discourse-smtp-address-do-mx-lookup/37839 "2016-01-12T16:28:57Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Blaisorblade](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/blaisorblade/32/107357_2.png) [@Blaisorblade](https://meta.discourse.org/u/Blaisorblade)\
**Post date:** [12 בינואר,‏ 2016,‏ 4:28pm UTC](https://meta.discourse.org/t/does-discourse-smtp-address-do-mx-lookup/37839/1 "2016-01-12T16:28:57Z")

</div>

What’s the content of DISCOURSE\_SMTP\_ADDRESS? Is it the actual hostname of the SMTP server, or can Discourse perform an MX lookup? I do need Discourse to do the MX lookup, and couldn’t find any actual info in docs, even though I tracked this down to [ActionMailer::Base](http://api.rubyonrails.org/classes/ActionMailer/Base.html). Docs mostly just talk of SMTP credentials. (For comparison, Postfix gives control over this behavior, while MSMTP just doesn’t support MX lookup on the relay host).

Unfortunately I can’t even try this out for now on my staging Discourse instance — it runs on the same physical server (our only one), and I can’t touch this because Docker/AUFS are causing not-yet-diagnosed instabilities: stopping my production Discourse instance fails and leaves it unusable until rebooting the host. (No, not my lucky day — and it was a bad idea to trust Docker to actually be robust).

---

_[View the full topic](https://meta.discourse.org/t/does-discourse-smtp-address-do-mx-lookup/37839)._
