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

[BUG] "setup-production" explains wrong EMAIL_BACKEND values #21

Open
Zocker1999NET opened this issue May 6, 2024 · 0 comments
Open
Labels
bug Something isn't working

Comments

@Zocker1999NET
Copy link

Zocker1999NET commented May 6, 2024

Describe the bug
The documentation setup-production.adoc (rendered) suggests invalid values for EMAIL_BACKEND. To quote:

EMAIL_BACKEND=console  # use an SMTP server or display the emails in the console (either "smtp" or "console")

However, the newest Taiga version fails to send any mails with EMAIL_BACKEND=smtp. The logs from the async container shows a Python import error, stating that smtp is invalid. By further investigation, I discovered that Taiga uses Django's mail backend, which describes correct & working values (e.g. EMAIL_BACKEND=django.core.mail.backends.smtp.EmailBackend).

How can we reproduce the behavior
Launch a Docker Taiga setup with EMAIL_BACKEND=smtp and valid SMTP credentials. Trigger a email notification and look for errors in the taiga-async container logs.

Workarounds
Use documentation from: https://docs.djangoproject.com/en/5.0/topics/email/

Taiga environment
Installed as described in taiga-docker.

Additional context
Neither the code from the Docker container's entrypoint nor from taiga-backend suggest that they use these environment variables. To me it seems that Django's mail backend does access these environment variables directly. Hence, IMO it would make sense to just link to the Django backend instead of copying their documentation into Taiga's documentation.

EDIT: It seems that PR #17 introduced this issue.

@Zocker1999NET Zocker1999NET added the bug Something isn't working label May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant