Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MAIL_URL and Administration -> EMail -> SMTP are both required for a working instance #6192

Closed
pierreozoux opened this issue Feb 28, 2017 · 3 comments

Comments

@pierreozoux
Copy link
Contributor

Rocket.Chat Version: latest

There are 2 ways to configure email in Rocket.chat:

  • MAIL_URL
  • Administration -> EMail -> SMTP

From my experience, they are both required and behave differently.
MAIL_URL is required to send "forgot password email" for instance, I believe, this is the standard meteor way.
Administration -> EMail -> SMTP is required to send verification email, this is I beliweve, something created by rocket, and not meteor standard..

This is related to #5192 and #3602

Would it be possible to make Administration -> EMail -> SMTP read from MAIL_URL?
And make MAIL_URL read from Administration -> EMail -> SMTP if not present?

This way, we would have a consistent way of configuring emails in Rocket.Chat.

@reetp
Copy link

reetp commented Feb 28, 2017

+1

@sampaiodiego
Copy link
Member

We actually create the env var MAIL_URL from Administration -> EMail -> SMTP values at runtime. So they are the same thing.

But yes, we could read from MAIL_URL to fill Administration -> EMail -> SMTP values.

@pierreozoux
Copy link
Contributor Author

@sampaiodiego thanks for your answer.

Actually the doc is pretty clear about it. As I know about MAIL_URL, it is strange for me as a meteor user.

I created this PR: RocketChat/docs-old#260 to simplify the doc, and remove reference to MAIL_URL as it is not really needed then.

@engelgabriel engelgabriel added this to the 0.56.0 milestone Apr 19, 2017
Cool-Dev121 added a commit to Cool-Dev121/docs that referenced this issue Mar 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants