Taiga on Docker, email not working

Troubleshooting Self hosted Taiga
21

I followed your steps and I am able to send an email but I don’t receive any email while commenting, changes status in the sprint board. Although, I can see following logs:
INFO/MainProcess] Task taiga.projects.notifications.tasks.send_bulk_email[f7986bc2-f413-4136-96de-d84fc1eff526] received

22

Hi there,

Taiga does not notify you of changes you make. Only changes others make, if you are assigned or watching the item.

Best regards!

1 Like
23

Thank you, it’s working

26

Hello
I had the same case, I even did the tests to send mail inside the taiga-back container and I got back the python error output, I solved it by adding the ip and domain of the SMTP in the /etc/hosts of taiga-back and inside the container, I did the mail test again and I got back 1 and the mail arrived to my inbox.

I hope it works, greetings.

root@b914cec3072f:/taiga-back# cat /etc/hosts
127.0.0.1  localhost
::1  localhost ip6-localhost ip6-loopback
fe00::0  ip6-localnet
ff00::0  ip6-mcastprefix
ff02::1  ip6-allnodes
ff02::2  ip6-allrouters
173.27.0.6  b914cec3072f
root@b914cec3072f:/taiga-back# echo "0.0.0.0       mail.domain.com" >> /etc/hosts
root@b914cec3072f:/taiga-back# cat /etc/hosts
127.0.0.1  localhost
::1  localhost ip6-localhost ip6-loopback
fe00::0  ip6-localnet
ff00::0  ip6-mcastprefix
ff02::1  ip6-allnodes
ff02::2  ip6-allrouters
173.27.0.6  b914cec3072f
0.0.0.0       mail.domain.com

imagen
imagen562×131 70.2 KB

27

I’m going crazy and I need your help.
Taiga is installed via portainer and everything went well with the installation. The problem is with email and I’ve tried almost everything.

root@15c1af7fe953:/taiga-back# python manage.py shell
Python 3.11.12 (main, Apr  9 2025, 18:23:23) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
(InteractiveConsole)
>>> from django.core.mail import send_mail
>>> send_mail("subject", "body", "helpdesk@domain.com", ["test@domain.com"])
Traceback (most recent call last):
  File "/opt/venv/lib/python3.11/site-packages/django/utils/module_loading.py", line 13, in import_string
    module_path, class_name = dotted_path.rsplit('.', 1)
    ^^^^^^^^^^^^^^^^^^^^^^^
ValueError: not enough values to unpack (expected 2, got 1)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/code.py", line 90, in runcode
    exec(code, self.locals)
  File "<console>", line 1, in <module>
  File "/opt/venv/lib/python3.11/site-packages/django/core/mail/__init__.py", line 52, in send_mail
    connection = connection or get_connection(
                               ^^^^^^^^^^^^^^^
  File "/opt/venv/lib/python3.11/site-packages/django/core/mail/__init__.py", line 34, in get_connection
    klass = import_string(backend or settings.EMAIL_BACKEND)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/venv/lib/python3.11/site-packages/django/utils/module_loading.py", line 15, in import_string
    raise ImportError("%s doesn't look like a module path" % dotted_path) from err
ImportError: smtp doesn't look like a module path
>>> 
now exiting InteractiveConsole...

I can’t understand what it means by “smtp doesn’t look like a module path” Please help!

28

Finally, for me, the solution was to edit the EMAIL_BACKEND setting in the Docker Compose file as follows.

EMAIL_BACKEND=django.core.mail.backends.smtp.EmailBackend