In a discussion about email deliverability in Discourse, RichardC asked whether the “notification email” setting referenced in the deliverability test refers to server-level or admin UI settings. pfaffman clarified that since recent versions of discourse-setup, this setting is configured via DISCOURSE_NOTIFICATION_EMAIL in app.yml and no longer appears in the admin UI. He proposed updating the test email template to reflect this change, suggesting users run discourse-setup or edit app.yml directly. codinghorror requested a concrete edit, which pfaffman provided, recommending clearer wording to guide users toward correct configuration. RichardC suggested adding clarification about domain validation for email providers. codinghorror consolidated the suggestions into a revised template and sought feedback from pfaffman and Falco, who approved the wording. pfaffman also recommended tweaking the phrasing to say “deliver mails from example.com” instead of “validate emails from example.com” for better clarity. The consensus supports updating the template to reflect current configuration practices and improve user guidance.
The first item in the Email Deliverability email is:
Be sure to set the notification email from: address correctly in your site settings. The domain specified in the “from” address of the emails you send is the domain your email will be validated against .
Does this refer to the server-level settings configured during install? Or something in the admin settings?
If you ran discourse-setup recently it asked you what address you wanted (suggesting the same default in the message), the notification_email is set by DISCOURSE_NOTIFICATION_EMAIL in your app.yml. And since it’s set that way, the setting no longer shows up in the UX.
To change it you’ll need to run discourse-setup or edit app.yml and rebuild (though ./launcher destroy app; ./launcher start app may work a bit faster if you haven’t done an upgrade from the command line).
This isn’t quite a bug, but it’s close.
@sam (or @codinghorror since we worked on this)-- someone needs to edit test_mailer.text_body_template accordingly. I think that it’s safe to just ignore the case where the setting isn’t in app.yml and tell people to run discourse-setup, as it seems unlikely that someone will go looking for this setting if it’s not wrong.
Be sure to set the notification email from: address correctly by running discourse-setup or changing DISCOURSE_NOTIFICATION_EMAIL in your app.yml. The domain specified in the “from” address of the emails you send is the domain your email will be validated against.
I’m very new to Discourse, but it would make more sense to me (assuming it’s accurate) to replace the second sentence with:
Use a from: email address domain that can be validated (e.g. if your from: email address is forum@example.com be sure your email provider can validate emails from example.com)
Be sure to set the notification email from: address correctly in your site settings. The domain specified in the “from” address of the emails you send is the domain your email will be validated against.
to
Be sure to set the notification email from: address correctly by running discourse-setup or changing DISCOURSE_NOTIFICATION_EMAIL in your app.yml. Use a from: email address domain that can be validated (e.g. if your from: email address is anything@example.com be sure your email provider can validate emails from example.com.)