Replies: 1 comment
-
|
See #703 (comment) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi FrePPLe community,
I’m running FrePPLe using the official Docker image and configuring it via docker-compose.yml.
I need to set up SMTP email sending using SSL (port 465) not TLS (which would be port 587).
I see that the environment variable FREPPLE_EMAIL_USE_TLS is supported in djangosettings.py, but there is no equivalent for SSL, e.g., FREPPLE_EMAIL_USE_SSL is not present in the code.
Questions:
How should I pass email SSL settings (host, port, user, password, and SSL/TLS choice) from my docker-compose.yml to the FrePPLe container?
Does FrePPLe (or its djangosettings.py) automatically switch to SSL if FREPPLE_EMAIL_USE_TLS is set to 'false' and port 465 is specified?
Or is there another environment variable or method required for SSL (not TLS)?
If I want to use port 465 with SSL (not TLS), do I need to modify djangosettings.py or is there a recommended way to mount or override settings for this scenario?
What is the exact expected behavior for FrePPLe/Django when only EMAIL_USE_TLS is provided and set to 'false'? Should I expect SSL to be used automatically, or does this default to plaintext?
Here’s an example from my docker-compose.yml:
environment:
FREPPLE_EMAIL_USE_TLS: 'false'
FREPPLE_EMAIL_HOST: mail.company.com
FREPPLE_EMAIL_PORT: '465'
FREPPLE_EMAIL_HOST_USER: myuser@domain.com
FREPPLE_EMAIL_HOST_PASSWORD: mypass
I have confirmed that using native Python and smtplib.SMTP_SSL works with my credentials and port 465, but the FrePPLe container fails with authentication or connection errors.
What is the correct and supported method for this setup? Do I need to patch the Django/FrePPLe settings or is there an officially recommended approach?
Thank you in advance.
Beta Was this translation helpful? Give feedback.
All reactions