While already having DISCOURSE_SMTP_ADDRESS
, what does the DISCOURSE_SMTP_DOMAIN
setting in containers/app.yml
do?
It’s not that desktop clients usually ask for “address” and “domain” separately, so I got confused.
While already having DISCOURSE_SMTP_ADDRESS
, what does the DISCOURSE_SMTP_DOMAIN
setting in containers/app.yml
do?
It’s not that desktop clients usually ask for “address” and “domain” separately, so I got confused.
I have the same question. I searched for an answer and I found this topic.
More specifically I wonder whether here we should put the same subdomain the Discourse instance has (discourse.example.com) or the domain (example.com). And whether this is something related to the SMTP configuration at all.
It is passed directly to action_mailer
Actions_Mailer’s Docs designate it as a part of SMTP conversation.
Is there a reason why this line in app.yml
DISCOURSE_SMTP_DOMAIN: discourse.example.com # (required by some providers)
isn’t asked during ./discourse-setup
and it isn’t commented either, introducing a false value in the configuration?
In case it helps future readers…
Replying to myself based on Emails have stopped sending - end of file reached - #25 by Falco, you need to add your mail domain i.e.
mail.example.com
.