# DISCOURSE\_MAIL\_ENDPOINT não atualiza após alterar o nome de domínio

**URL:** <https://meta.discourse.org/t/discourse-mail-endpoint-not-updating-after-changing-domain-name/124001>\
**Category:** Support\
**Created:** [Julho 25, 2019, 10:25pm UTC](https://meta.discourse.org/t/discourse-mail-endpoint-not-updating-after-changing-domain-name/124001 "2019-07-25T22:25:30Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![eddowding](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eddowding/32/142788_2.png) [@eddowding](https://meta.discourse.org/u/eddowding)\
**Post date:** [Julho 25, 2019, 10:25pm UTC](https://meta.discourse.org/t/discourse-mail-endpoint-not-updating-after-changing-domain-name/124001/1 "2019-07-25T22:25:30Z")

</div>

Fui obrigado a alterar o nome de domínio em um servidor Discourse que configurei. Ele estava configurado para receber e-mails (diretamente, não via POP3).

Editei os arquivos mail-receiver.yml e app.yml e recriei o aplicativo para usar o novo nome de domínio ([newname.com](http://newname.com)), mas ao reiniciar o mail-receiver, os logs ainda mostram que ele está usando as configurações antigas ([kinnship.org](http://kinnship.org)) para DISCOURSE\_MAIL\_ENDPOINT, DISCOURSE\_API\_KEY e MAIL\_DOMAIN.

Alguma dica de como corrigir isso? Obrigado!

```
<22>Jul 25 22:01:58 postfix/anvil[89]: estatísticas: tamanho máximo do cache 2 em Jul 25 21:52:13
Ambiente de execução:
HOSTNAME=discourse-kinship-mail-receiver
GEM_HOME=/usr/local/bundle
TERM=xterm
BUNDLE_SILENCE_ROOT_WARNING=1
BUNDLE_APP_CONFIG=/usr/local/bundle
PATH=/usr/local/bundle/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin RUBY_DOWNLOAD_SHA256=341cd9032e9fd17c452ed8562a8d43f7e45bfe05e411d0d7d627751dd82c578c
DOCKER_HOST_IP=172.17.0.1
PWD=/
DISCOURSE_API_USERNAME=system
LANG=en_US.UTF-8
RUBY_MAJOR=2.3
RUBYGEMS_VERSION=2.6.11
BUNDLE_BIN=/usr/local/bundle/bin
SHLVL=1
HOME=/root
DISCOURSE_MAIL_ENDPOINT=https://kinnship.org/admin/email/handle_mail
DISCOURSE_API_KEY=xxxxxxxxxxxx
BUNDLE_PATH=/usr/local/bundle
MAIL_DOMAIN=kinnship.org
RUBY_VERSION=2.3.4
BUNDLER_VERSION=1.14.6
_=/usr/bin/env
Entregando e-mail enviado para kinnship.org ao Discourse
Iniciando o Postfix
<22>Jul 25 22:04:05 postfix/master[1]: daemon iniciado -- versão 3.1.1, configuração /etc/postfix

```

---

<div class="post-metadata">

**Author:** ![JimPas](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jimpas/32/148179_2.png) [@JimPas](https://meta.discourse.org/u/JimPas)\
**Post date:** [Julho 25, 2019, 10:50pm UTC](https://meta.discourse.org/t/discourse-mail-endpoint-not-updating-after-changing-domain-name/124001/2 "2019-07-25T22:50:03Z")

</div>

Vejo uma grafia de “kinship” na linha HOSTNAME=discourse- **kinship** -mail-receiver

Vejo uma grafia diferente em: “DISCOURSE\_MAIL\_ENDPOINT=https:// **kinnship**.org/…”

Mais abaixo, nas linhas DISCOURSE\_API\_KEY, há 2 "n"s em “kinship”:  
"MAIL\_DOMAIN= **kinnship**.org  
“Entregando e-mails enviados para **kinnship**.org ao Discourse”

Ou você perdeu um “n” na primeira linha, ou as outras 3 linhas têm um “n” extra no nome de domínio.

---

<div class="post-metadata">

**Author:** ![eddowding](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eddowding/32/142788_2.png) [@eddowding](https://meta.discourse.org/u/eddowding)\
**Post date:** [Julho 25, 2019, 10:59pm UTC](https://meta.discourse.org/t/discourse-mail-endpoint-not-updating-after-changing-domain-name/124001/3 "2019-07-25T22:59:59Z")

</div>

Ah, um ponto-chave que eu deveria ter dito no original é que o novo nome de domínio é completamente diferente! Este é o antigo.

---

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [Julho 25, 2019, 11:09pm UTC](https://meta.discourse.org/t/discourse-mail-endpoint-not-updating-after-changing-domain-name/124001/4 "2019-07-25T23:09:05Z")

</div>

> [@eddowding](#):
>
> quando reinicio o mail-receiver,

Não consigo dizer se você sabe disso, mas você deveria

```
./launcher rebuild mail-receiver

```

Embora

```
 ./launcher destroy mail-receiver
 ./launcher start mail-receiver

```

provavelmente funcionaria.

---

<div class="post-metadata">

**Author:** ![eddowding](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eddowding/32/142788_2.png) [@eddowding](https://meta.discourse.org/u/eddowding)\
**Post date:** [Julho 25, 2019, 11:23pm UTC](https://meta.discourse.org/t/discourse-mail-endpoint-not-updating-after-changing-domain-name/124001/5 "2019-07-25T23:23:30Z")

</div>

> [@pfaffman](#):
>
> ./launcher rebuild mail-receiver

Você é incrível! Eu estava fazendo ./launcher bootstrap mail-receiver achando que fazia a mesma coisa. Épico! Obrigado!

(Agora é esquecer aquelas 3 horas que gastei tentando e que nunca mais vou recuperar..!)

---

<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:** [Agosto 24, 2019, 11:25pm UTC](https://meta.discourse.org/t/discourse-mail-endpoint-not-updating-after-changing-domain-name/124001/6 "2019-08-24T23:25:44Z")

</div>

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