-
Notifications
You must be signed in to change notification settings - Fork 641
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
Allow SMTP Port in Email Settings to be set to an environment variable #3740
Comments
Correct. Is that something you need to set for each environment? Seems like 99% of the time the standard ports are used. |
We use Mailtrap ( ( |
I'm also looking into this. Locally, I use my gmail to test, but on the production server, it has it's own SMTP server that I can't use locally (blocked to localhost). I would like to be able to set the transport type somehow, and the port would be required too at this point. EDIT: I have to add that I'm using the project.yaml file so this also gets saved there, which overwrites the transport type on my prod server. |
Alright, as of the next release it will be possible to set Port to an environment variable. |
Any chance that will include a way to set the transport type too? I would love to use the project config file, but impossible for me without a way to save that in a config. |
No that wouldn’t be possible; that’s why we allow you to override the mailer transport at runtime. |
Description
With 3.1 we can now use environment variables for SMTP email settings. But this feature was not extended to the SMTP Port field. Different SMTP configurations on dev and production cannot truly live in the
.env
file if both SMTP servers do not share the same port (e.g. Mailgun on production uses 587, but Mailtrap on dev uses 465).Steps to reproduce
SMTP
.env
file, like$SMTP_PORT
Additional info
The text was updated successfully, but these errors were encountered: