starred/planka
1
0
Fork 0
mirror of https://github.com/plankanban/planka.git synced 2026-02-25 03:14:50 +03:00
Code Issues 396 Packages Projects Releases 16 Wiki Activity

[Bug]: Planka does not send mail via SMTP, no SMTP logs #734

New Issue
Open
opened 2026-02-04 21:08:09 +03:00 by OVERLORD · 13 comments
OVERLORD commented 2026-02-04 21:08:09 +03:00
Owner
Copy Link

Originally created by @romdev-kg on GitHub (Jun 10, 2025).

Where is the problem occurring?

None

What browsers are you seeing the problem on?

No response

Current behavior

Planka is running in Docker, all SMTP environment variables are set correctly (SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASSWORD, SMTP_FROM, SMTP_NAME, SMTP_SECURE).
Tried different SMTP servers and ports, changed SMTP_SECURE, added SMTP_NAME.
No emails are sent, and there are no SMTP-related messages in Planka logs (no errors, no attempts to send mail).
Mail-triggering events definitely occur (card subscription, action by another user).

What I tried:

Double-checked variable names (SMTP_PASSWORD, not SMTP_PASS).

Restarted container after changes.

Using latest Planka image (2.0.0-rc.3).

Verified SMTP server is accessible from host (telnet and swaks work).

Logs only show standard debug messages, nothing about SMTP.

Expected:

When trying to send an email, logs should show either success or error.

Email should be sent, or an error should be visible.

Actual behavior:

No emails, no logs about sending attempts.

Questions:

How can I force Planka to test SMTP and show logs?

Why are there no logs about sending attempts?

Is there a way to enable verbose SMTP logging?

environment:

Desired behavior

No response

Steps to reproduce

Steps to reproduce
Deploy Planka using the official Docker image and docker-compose.

Set up SMTP environment variables as described in the documentation.

Register a single user with a valid email address.

Create a board and add several cards.

Subscribe (watch) your own cards.

Move your own cards between columns and/or add comments to them as the same user.

Check your mailbox and review Planka logs for any SMTP activity.

Expected result:
An email notification is sent to the user’s email address when cards are moved or commented.

Actual result:
No email is received, and there are no SMTP-related messages or errors in the logs.

Other information

No response

Originally created by @romdev-kg on GitHub (Jun 10, 2025). ### Where is the problem occurring? None ### What browsers are you seeing the problem on? _No response_ ### Current behavior Planka is running in Docker, all SMTP environment variables are set correctly (SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASSWORD, SMTP_FROM, SMTP_NAME, SMTP_SECURE). Tried different SMTP servers and ports, changed SMTP_SECURE, added SMTP_NAME. No emails are sent, and there are no SMTP-related messages in Planka logs (no errors, no attempts to send mail). Mail-triggering events definitely occur (card subscription, action by another user). What I tried: Double-checked variable names (SMTP_PASSWORD, not SMTP_PASS). Restarted container after changes. Using latest Planka image (2.0.0-rc.3). Verified SMTP server is accessible from host (telnet and swaks work). Logs only show standard debug messages, nothing about SMTP. Expected: When trying to send an email, logs should show either success or error. Email should be sent, or an error should be visible. Actual behavior: No emails, no logs about sending attempts. Questions: How can I force Planka to test SMTP and show logs? Why are there no logs about sending attempts? Is there a way to enable verbose SMTP logging? environment: - SMTP_HOST=your_smtp_server - SMTP_PORT=your_port - SMTP_USER=your_email@example.com - SMTP_PASSWORD=your_password - SMTP_FROM=your_email@example.com - SMTP_NAME=your_name_or_login - SMTP_SECURE=false ### Desired behavior _No response_ ### Steps to reproduce Steps to reproduce Deploy Planka using the official Docker image and docker-compose. Set up SMTP environment variables as described in the documentation. Register a single user with a valid email address. Create a board and add several cards. Subscribe (watch) your own cards. Move your own cards between columns and/or add comments to them as the same user. Check your mailbox and review Planka logs for any SMTP activity. Expected result: An email notification is sent to the user’s email address when cards are moved or commented. Actual result: No email is received, and there are no SMTP-related messages or errors in the logs. ### Other information _No response_
OVERLORD commented 2026-02-04 21:08:21 +03:00
Author
Owner
Copy Link

@meltyshev commented on GitHub (Jun 10, 2025):

Hi! Thanks for reporting this. I'll test all the SMTP-related things once again.

@meltyshev commented on GitHub (Jun 10, 2025): Hi! Thanks for reporting this. I'll test all the SMTP-related things once again.
OVERLORD commented 2026-02-04 21:08:37 +03:00
Author
Owner
Copy Link

@stufently commented on GitHub (Jun 15, 2025):

Any news? Have same problem

@stufently commented on GitHub (Jun 15, 2025): Any news? Have same problem
OVERLORD commented 2026-02-04 21:08:45 +03:00
Author
Owner
Copy Link

@meltyshev commented on GitHub (Jun 16, 2025):

I've just tested this in the production environment, and everything works fine for me. I also see all the logs in the console if something is misconfigured:

planka-1    | 2025-06-16 20:15:02 [E] Error sending email: Error: Missing credentials for "PLAIN"
@meltyshev commented on GitHub (Jun 16, 2025): I've just tested this in the production environment, and everything works fine for me. I also see all the logs in the console if something is misconfigured: ``` planka-1 | 2025-06-16 20:15:02 [E] Error sending email: Error: Missing credentials for "PLAIN" ```
OVERLORD commented 2026-02-04 21:08:54 +03:00
Author
Owner
Copy Link

@juanjullian commented on GitHub (Jul 7, 2025):

I can ever see any logs in planka.log about that

@juanjullian commented on GitHub (Jul 7, 2025): I can ever see any logs in planka.log about that
OVERLORD commented 2026-02-04 21:09:01 +03:00
Author
Owner
Copy Link

@dmaus commented on GitHub (Sep 4, 2025):

Any news about this? I dont see any logging about mail sending (2.0.0-rc.3), nor does the SMTP work at all.
docker logs -f planka-planka-1 2025-09-04 07:29:11 [I] Initializing custom hook ('current-user') 2025-09-04 07:29:11 [I] Initializing custom hook ('file-manager') 2025-09-04 07:29:11 [I] Initializing custom hook ('query-methods') 2025-09-04 07:29:11 [I] Initializing custom hook ('smtp') 2025-09-04 07:29:11 [I] Initializing custom hook ('watcher')
No matter what i do, nothing else gets logged (- LOG_LEVEL=debug)

@dmaus commented on GitHub (Sep 4, 2025): Any news about this? I dont see any logging about mail sending (2.0.0-rc.3), nor does the SMTP work at all. `docker logs -f planka-planka-1 2025-09-04 07:29:11 [I] Initializing custom hook ('current-user') 2025-09-04 07:29:11 [I] Initializing custom hook ('file-manager') 2025-09-04 07:29:11 [I] Initializing custom hook ('query-methods') 2025-09-04 07:29:11 [I] Initializing custom hook ('smtp') 2025-09-04 07:29:11 [I] Initializing custom hook ('watcher') ` No matter what i do, nothing else gets logged `(- LOG_LEVEL=debug)`
OVERLORD commented 2026-02-04 21:09:08 +03:00
Author
Owner
Copy Link

@meltyshev commented on GitHub (Sep 5, 2025):

Any news about this? I dont see any logging about mail sending (2.0.0-rc.3), nor does the SMTP work at all. docker logs -f planka-planka-1 2025-09-04 07:29:11 [I] Initializing custom hook ('current-user') 2025-09-04 07:29:11 [I] Initializing custom hook ('file-manager') 2025-09-04 07:29:11 [I] Initializing custom hook ('query-methods') 2025-09-04 07:29:11 [I] Initializing custom hook ('smtp') 2025-09-04 07:29:11 [I] Initializing custom hook ('watcher') No matter what i do, nothing else gets logged (- LOG_LEVEL=debug)

Hi! We've seen this issue a few times where there are no logs when sending emails, but whenever we try to reproduce it, an error does appear during sending... It's a bit difficult to investigate the root cause without seeing all the actions performed and the configuration.

It's also possible that email sending isn't triggered at all, since only 4 actions currently trigger emails: moving a card, commenting on a card, adding a member to a card, and mentioning in a comment (the last one hasn't been released yet). Additionally, actions performed by the current user do not trigger emails for that user.

@meltyshev commented on GitHub (Sep 5, 2025): > Any news about this? I dont see any logging about mail sending (2.0.0-rc.3), nor does the SMTP work at all. `docker logs -f planka-planka-1 2025-09-04 07:29:11 [I] Initializing custom hook ('current-user') 2025-09-04 07:29:11 [I] Initializing custom hook ('file-manager') 2025-09-04 07:29:11 [I] Initializing custom hook ('query-methods') 2025-09-04 07:29:11 [I] Initializing custom hook ('smtp') 2025-09-04 07:29:11 [I] Initializing custom hook ('watcher') ` No matter what i do, nothing else gets logged `(- LOG_LEVEL=debug)` Hi! We've seen this issue a few times where there are no logs when sending emails, but whenever we try to reproduce it, an error does appear during sending... It's a bit difficult to investigate the root cause without seeing all the actions performed and the configuration. It's also possible that email sending isn't triggered at all, since only 4 actions currently trigger emails: moving a card, commenting on a card, adding a member to a card, and mentioning in a comment (the last one hasn't been released yet). Additionally, actions performed by the current user do not trigger emails for that user.
OVERLORD commented 2026-02-04 21:09:11 +03:00
Author
Owner
Copy Link

@talondnb commented on GitHub (Sep 5, 2025):

If it helps, here's my working SMTP configs using gmail:

docker-compose.yml:

      # Email Notifications (https://nodemailer.com/smtp/)
      - SMTP_HOST=${SMTP_HOST}
      - SMTP_PORT=${SMTP_PORT}
      - SMTP_NAME=${SMTP_NAME}
      - SMTP_SECURE=${SMTP_SECURE}
      - SMTP_USER=${SMTP_USER}
      - SMTP_PASSWORD=${SMTP_PASSWORD}

.env:

SMTP_HOST=smtp.gmail.com
SMTP_PORT=465
SMTP_SECURE=true
SMTP_USER=blah@gmail.com
SMTP_PASSWORD=blah
SMTP_FROM="'Planka' <noreply@blah.id.ru>"
SMTP_NAME=gmail.com

..and confirmed as above as well, not a lot of actions trigger the email. The most obvious I've faced is when assigning a member to a card.

@talondnb commented on GitHub (Sep 5, 2025): If it helps, here's my working SMTP configs using gmail: docker-compose.yml: ``` # Email Notifications (https://nodemailer.com/smtp/) - SMTP_HOST=${SMTP_HOST} - SMTP_PORT=${SMTP_PORT} - SMTP_NAME=${SMTP_NAME} - SMTP_SECURE=${SMTP_SECURE} - SMTP_USER=${SMTP_USER} - SMTP_PASSWORD=${SMTP_PASSWORD} ``` .env: ``` SMTP_HOST=smtp.gmail.com SMTP_PORT=465 SMTP_SECURE=true SMTP_USER=blah@gmail.com SMTP_PASSWORD=blah SMTP_FROM="'Planka' <noreply@blah.id.ru>" SMTP_NAME=gmail.com ``` ..and confirmed as above as well, not a lot of actions trigger the email. The most obvious I've faced is when assigning a member to a card.
OVERLORD commented 2026-02-04 21:09:14 +03:00
Author
Owner
Copy Link

@AnthonyLELUYER commented on GitHub (Oct 14, 2025):

Hello,

Same issue, except I have some weird logs:

Warning: Adapter sent back a uniqueness error, but that error references key(s) (card_id, user_id) which cannot
be matched up with the column names of any attributes in this model (`cardsubscription`).  This probably
means there is a bug in this adapter.
(Note for adapter implementors: If your adapter doesn't support granular reporting of the keys violated
in uniqueness errors, then just use an empty array for the `keys` property of this error.)
(Proceeding anyway as if these keys weren't included...)

Here is my conf:

      # Email Notifications (https://nodemailer.com/smtp/)
      - SMTP_HOST=smtp.gmail.com
      - SMTP_FROM=mail-sender@domain.fr
      - SMTP_PORT=465
      - SMTP_USER=mail-sender@domain.fr
      - SMTP_NAME=gmail.com
      - SMTP_SECURE=true
      - SMTP_PASSWORD="password"
@AnthonyLELUYER commented on GitHub (Oct 14, 2025): Hello, Same issue, except I have some weird logs: ``` Warning: Adapter sent back a uniqueness error, but that error references key(s) (card_id, user_id) which cannot be matched up with the column names of any attributes in this model (`cardsubscription`). This probably means there is a bug in this adapter. (Note for adapter implementors: If your adapter doesn't support granular reporting of the keys violated in uniqueness errors, then just use an empty array for the `keys` property of this error.) (Proceeding anyway as if these keys weren't included...) ``` Here is my conf: ``` # Email Notifications (https://nodemailer.com/smtp/) - SMTP_HOST=smtp.gmail.com - SMTP_FROM=mail-sender@domain.fr - SMTP_PORT=465 - SMTP_USER=mail-sender@domain.fr - SMTP_NAME=gmail.com - SMTP_SECURE=true - SMTP_PASSWORD="password" ```
OVERLORD commented 2026-02-04 21:09:19 +03:00
Author
Owner
Copy Link

@meltyshev commented on GitHub (Oct 14, 2025):

Hello,

Same issue, except I have some weird logs:

Warning: Adapter sent back a uniqueness error, but that error references key(s) (card_id, user_id) which cannot
be matched up with the column names of any attributes in this model (`cardsubscription`).  This probably
means there is a bug in this adapter.
(Note for adapter implementors: If your adapter doesn't support granular reporting of the keys violated
in uniqueness errors, then just use an empty array for the `keys` property of this error.)
(Proceeding anyway as if these keys weren't included...)

Here is my conf:

      # Email Notifications (https://nodemailer.com/smtp/)
      - SMTP_HOST=smtp.gmail.com
      - SMTP_FROM=mail-sender@domain.fr
      - SMTP_PORT=465
      - SMTP_USER=mail-sender@domain.fr
      - SMTP_NAME=gmail.com
      - SMTP_SECURE=true
      - SMTP_PASSWORD="password"

Hi! This warning isn't related to the SMTP, and we've already fixed it. Also, we've added SMTP configuration right in the UI, and you can test the connection there (and see the connection test log), so it'll be easier to debug. It should be released soon in the final v2 version. By the way, you can already try the UI configuration by switching to the nightly build - just don't forget to switch back to the stable version once it's released.

@meltyshev commented on GitHub (Oct 14, 2025): > Hello, > > Same issue, except I have some weird logs: > > ``` > Warning: Adapter sent back a uniqueness error, but that error references key(s) (card_id, user_id) which cannot > be matched up with the column names of any attributes in this model (`cardsubscription`). This probably > means there is a bug in this adapter. > (Note for adapter implementors: If your adapter doesn't support granular reporting of the keys violated > in uniqueness errors, then just use an empty array for the `keys` property of this error.) > (Proceeding anyway as if these keys weren't included...) > ``` > > Here is my conf: > > ``` > # Email Notifications (https://nodemailer.com/smtp/) > - SMTP_HOST=smtp.gmail.com > - SMTP_FROM=mail-sender@domain.fr > - SMTP_PORT=465 > - SMTP_USER=mail-sender@domain.fr > - SMTP_NAME=gmail.com > - SMTP_SECURE=true > - SMTP_PASSWORD="password" > ``` Hi! This warning isn't related to the SMTP, and we've already fixed it. Also, we've added SMTP configuration right in the UI, and you can test the connection there (and see the connection test log), so it'll be easier to debug. It should be released soon in the final v2 version. By the way, you can already try the UI configuration by switching to the `nightly` build - just don't forget to switch back to the stable version once it's released.
OVERLORD commented 2026-02-04 21:09:21 +03:00
Author
Owner
Copy Link

@AnthonyLELUYER commented on GitHub (Oct 14, 2025):

Nice thank you!
I switched to nightly but I can't find the SMTP config in UI. Under "Administration", I only have "Users" and "Webhooks".

@AnthonyLELUYER commented on GitHub (Oct 14, 2025): Nice thank you! I switched to nightly but I can't find the SMTP config in UI. Under "Administration", I only have "Users" and "Webhooks".
OVERLORD commented 2026-02-04 21:09:29 +03:00
Author
Owner
Copy Link

@meltyshev commented on GitHub (Oct 14, 2025):

Nice thank you!
I switched to nightly but I can't find the SMTP config in UI. Under "Administration", I only have "Users" and "Webhooks".

Oops, forgot to mention that the new SMTP tab will only be visible if SMTP_* environment variables are commented out.

@meltyshev commented on GitHub (Oct 14, 2025): > Nice thank you! > I switched to nightly but I can't find the SMTP config in UI. Under "Administration", I only have "Users" and "Webhooks". Oops, forgot to mention that the new SMTP tab will only be visible if SMTP_* environment variables are commented out.
OVERLORD commented 2026-02-04 21:09:32 +03:00
Author
Owner
Copy Link

@AnthonyLELUYER commented on GitHub (Oct 15, 2025):

Perfect, works great, thanks a lot!

@AnthonyLELUYER commented on GitHub (Oct 15, 2025): Perfect, works great, thanks a lot!
OVERLORD commented 2026-02-04 21:09:35 +03:00
Author
Owner
Copy Link

@goldmont commented on GitHub (Dec 19, 2025):

Nice thank you!
I switched to nightly but I can't find the SMTP config in UI. Under "Administration", I only have "Users" and "Webhooks".

Oops, forgot to mention that the new SMTP tab will only be visible if SMTP_* environment variables are commented out.

Hi,

I have no SMTP_* variables but I still cannot see the SMTP tab (2.0.0-rc.4).

@goldmont commented on GitHub (Dec 19, 2025): > > Nice thank you! > > I switched to nightly but I can't find the SMTP config in UI. Under "Administration", I only have "Users" and "Webhooks". > > Oops, forgot to mention that the new SMTP tab will only be visible if SMTP_* environment variables are commented out. Hi, I have no SMTP_* variables but I still cannot see the SMTP tab (2.0.0-rc.4).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
documentation
documentation
duplicate
enhancement
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#734
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?