# Suggestion - allow optional system email "from" setting during setup

**URL:** <https://meta.discourse.org/t/suggestion-allow-optional-system-email-from-setting-during-setup/52803>\
**Category:** Feature\
**Created:** [2016 年 11 月 11 日午後 2:36 UTC](https://meta.discourse.org/t/suggestion-allow-optional-system-email-from-setting-during-setup/52803 "2016-11-11T14:36:16Z")\
**Posts on this page:** 1\
**Showing post:** 7

<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:** [2016 年 11 月 14 日午後 8:02 UTC](https://meta.discourse.org/t/suggestion-allow-optional-system-email-from-setting-during-setup/52803/7 "2016-11-14T20:02:47Z")

</div>

> [@sam](#):
>
> Perhaps a more effective direction that would improve quality of life for every installer is to host a “free for all” SMTP install API for use during setup. The huge upside would be that we could move SMTP config out of ENV and into the UI.

Oh, **that’s** why mail config is in that yaml file? I guess I hadn’t really stopped to consider why it was there. I had an install customer just yesterday say “Well, obviously, if I get logged in I can change the mail config from the UI.”

It doesn’t seem that dangerous to allow the first admin to log in without email verification. For the site to be hijacked the hijacker would have to find the site before it got configured **and** know the email address(es) of the admins listed in the yaml file. Pretty much every other web app that I can think of just lets whoever gets there first potentially hijack the site. You could still have email verification be on of the things in the “your site is broken” checklist.

---

_[View the full topic](https://meta.discourse.org/t/suggestion-allow-optional-system-email-from-setting-during-setup/52803)._
