Allow update smtp settings in admin panel

email

(Kevin Yang) #1

Email is such a messy and buggy system, since i have to debug the email system problem once awhile, it would be convenient to provide an easy settings in admin panel. rather than to rebuild the whole docker app. I dont understand why email setting is a set-once option.


Allow changing SMTP provider without recompiling app
(Allen - Watchman Monitoring) #2

Agreed that it would be great to adjust this in the admin… I’m guessing there are reasons why it’s not like that already.

Recently I learned the following which should help… the word destroy is scary to me, but the source of tip couldn’t be better:


#3

I had some problems with SMTP and had to figure out a lot of things to make it work. Adding these settings to the Admin panel would be great. Totally support that.

Maybe also add an option to do ./launcher start app


(Felix Freiberger) #4

How should this work, exactly? SMTP settings are in app.yml, and they need to stay there because they are meant to be configured during set up, before the first administrator account is created. I don’t think that it’s reasonable for Discourse to find and update its own app.yml file, so what alternatives are there?

The only reasonable way to do this that I see would be a site sitting for “ignore the SMTP configuration in the container definition and use these settings instead”, which sounds like a support nightmare to me (since now there are two places where the mail configuration could be messed up).


(Kevin Yang) #5

@fefrei i guess security is the reason you guys put smtp settings in app.yml.

If that 's true, i would simplified that design and put an use-and-forget ‘secret-key’ in app.yml, the first access user must provide this secret key to access the register page(only one person get this key, and it will never be used agaign). And before actual register, this user must provide the system smtp settings, these settings will be saved just like all the other settings in admin panel.


(Dean Taylor) #6

This feature request is also relevant to multisite installs as per this support thread: