# 通过 domain.com 由 noreply@(IP 地址) 发送的电子邮件

**URL:** https://meta.discourse.org/t/emails-sent-from-noreply-ip-address-via-domain-com/87506
**Category:** Support
**Created:** [2018年五月15日 02:46 UTC](https://meta.discourse.org/t/emails-sent-from-noreply-ip-address-via-domain-com/87506 "2018-05-15T02:46:38Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![cmwebdev](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cmwebdev/32/122368_2.png) [@cmwebdev](https://meta.discourse.org/u/cmwebdev)
#### Post date: [2018年五月15日 02:46 UTC](https://meta.discourse.org/t/emails-sent-from-noreply-ip-address-via-domain-com/87506/1 "2018-05-15T02:46:38Z")

</div>

I’m sending Discourse emails through Elastic Email. I noticed that when they arrive in my inbox, the “From” field says **[noreply@0.0.0.0](mailto:noreply@0.0.0.0) via [domain.com](http://domain.com)** (with the real IP and domain that my discourse install uses).

Is this normal for Discourse to send it like that with the IP address instead of from **[noreply@domain.com](mailto:noreply@domain.com)**? Or do I have something configured incorrectly? 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: [2018年五月15日 03:27 UTC](https://meta.discourse.org/t/emails-sent-from-noreply-ip-address-via-domain-com/87506/2 "2018-05-15T03:27:58Z")

</div>

Check 2 things:

1. `Notification Email` in Your Discourse settings.
2. Verify your domain with elasticemail to remove via part.

---

<div class="post-metadata">

### Author: ![cmwebdev](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cmwebdev/32/122368_2.png) [@cmwebdev](https://meta.discourse.org/u/cmwebdev)
#### Post date: [2018年五月15日 03:33 UTC](https://meta.discourse.org/t/emails-sent-from-noreply-ip-address-via-domain-com/87506/3 "2018-05-15T03:33:44Z")

</div>

Thanks! It was the notification email. I guess it was still set to the IP address from when I first setup the container. Didn’t see that setting when I looked for it.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2018年五月15日 03:49 UTC](https://meta.discourse.org/t/emails-sent-from-noreply-ip-address-via-domain-com/87506/4 "2018-05-15T03:49:31Z")

</div>

No official setup routine that I know of ever sets that to an IP address. Are you on an unsupported install?

---

<div class="post-metadata">

### Author: ![cmwebdev](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cmwebdev/32/122368_2.png) [@cmwebdev](https://meta.discourse.org/u/cmwebdev)
#### Post date: [2018年五月15日 04:01 UTC](https://meta.discourse.org/t/emails-sent-from-noreply-ip-address-via-domain-com/87506/5 "2018-05-15T04:01:23Z")

</div>

I used the one click install from Digital Ocean which I believe is supported? It was definitely no fault of any setup routine that it ended up as an IP address. That was my doing.

When I setup the container I first used the IP address for `DISCOURSE_HOSTNAME` instead of the domain name because it was a migration from an SMF forum that I was trying to keep online as long as possible before the migration.

I setup the DO container first so it was ready to go. Then I took the SMF forum offline and migrated it to my local Vagrant Discourse. Then I exported, changed the DNS to point to the DO container and changed the `DISCOURSE_HOSTNAME` to the actual domain name.

---

<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: [2018年五月15日 04:07 UTC](https://meta.discourse.org/t/emails-sent-from-noreply-ip-address-via-domain-com/87506/6 "2018-05-15T04:07:37Z")

</div>

The only official setup method I know of is doing it by hand following the 30 minutes install Guide.

Digitalocean’s image is sometimes heavily outdated and needs to be updated.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2018年五月15日 04:24 UTC](https://meta.discourse.org/t/emails-sent-from-noreply-ip-address-via-domain-com/87506/7 "2018-05-15T04:24:16Z")

</div>

> [@cmwebdev](#):
>
> When I setup the container I first used the IP address for `DISCOURSE_HOSTNAME` instead of the domain name because it was a migration from an SMF forum that I was trying to keep online as long as possible before the migration.

Oh I see but FYI running from an ip address is not supported.

---

<div class="post-metadata">

### Author: ![cmwebdev](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cmwebdev/32/122368_2.png) [@cmwebdev](https://meta.discourse.org/u/cmwebdev)
#### Post date: [2018年五月15日 04:28 UTC](https://meta.discourse.org/t/emails-sent-from-noreply-ip-address-via-domain-com/87506/8 "2018-05-15T04:28:35Z")

</div>

Ya it was only ever used by me, the admin, during setup. Besides me not knowing or forgetting to change the notification email address, it was a smooth transition from the IP to the domain name.

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [2024年六月8日 12:37 UTC](https://meta.discourse.org/t/emails-sent-from-noreply-ip-address-via-domain-com/87506/9 "2024-06-08T12:37:27Z")

</div>

此主题已在 2216 天后自动关闭。不再允许回复。
