The email sending tool has a problem when it is set for the first time. Delete the node and cannot modify the mailbox configuration again. It is always on this page #7051

Closed
opened 2026-02-21 18:18:37 -05:00 by yindo · 2 comments
Owner

Originally created by @luxi001-aaa on GitHub (Dec 4, 2024).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.12.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

1733309237180

✔️ Expected Behavior

No response

Actual Behavior

No response

Originally created by @luxi001-aaa on GitHub (Dec 4, 2024). ### Self Checks - [X] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:) - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.12.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ![1733309237180](https://github.com/user-attachments/assets/57f08201-4cf0-4199-a297-4749801deba8) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:18:37 -05:00
yindo closed this issue 2026-02-21 18:18:37 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Dec 4, 2024):

The issue you're experiencing with the email sending tool in Dify version 0.12.1, where you cannot modify the mailbox configuration after deleting a node, might be related to how the email configuration is managed within the system. Unfortunately, I couldn't find specific information on how node deletion affects email configuration or any related error messages in the documentation or codebase.

However, to modify the email configuration, you typically need to update the relevant parameters in the .env file and restart the service using the following commands:

docker compose down
docker compose up -d

Ensure that all necessary email configuration fields are correctly set, such as MAIL_TYPE, SMTP_SERVER, SMTP_PORT, and others, as missing or incorrect settings can lead to issues [1].

If the problem persists, it might be beneficial to check the logs for any error messages that could provide more insight into the issue. Additionally, reviewing the configuration files mentioned in the documentation, such as docker-legacy/docker-compose.yaml and api/configs/feature/__init__.py, might help identify any misconfigurations [2][3].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Dec 4, 2024): <!-- Answer --> The issue you're experiencing with the email sending tool in Dify version 0.12.1, where you cannot modify the mailbox configuration after deleting a node, might be related to how the email configuration is managed within the system. Unfortunately, I couldn't find specific information on how node deletion affects email configuration or any related error messages in the documentation or codebase. However, to modify the email configuration, you typically need to update the relevant parameters in the `.env` file and restart the service using the following commands: ```bash docker compose down docker compose up -d ``` Ensure that all necessary email configuration fields are correctly set, such as `MAIL_TYPE`, `SMTP_SERVER`, `SMTP_PORT`, and others, as missing or incorrect settings can lead to issues <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/faqs.md)</sup>. If the problem persists, it might be beneficial to check the logs for any error messages that could provide more insight into the issue. Additionally, reviewing the configuration files mentioned in the documentation, such as `docker-legacy/docker-compose.yaml` and `api/configs/feature/__init__.py`, might help identify any misconfigurations <sup>[[2]](https://github.com/langgenius/dify/blob/main/docker-legacy/docker-compose.yaml)</sup><sup>[[3]](https://github.com/langgenius/dify/blob/main/api/configs/feature/__init__.py)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
Author
Owner

@crazywoola commented on GitHub (Dec 4, 2024):

This can be set in this page https://cloud.dify.ai/tools. I guess this is what you are looking for, you can remove the configuration for the mail tool here, the configuration panel inside the workflow is a short cut to this page.

@crazywoola commented on GitHub (Dec 4, 2024): This can be set in this page https://cloud.dify.ai/tools. I guess this is what you are looking for, you can remove the configuration for the mail tool here, the configuration panel inside the workflow is a short cut to this page.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#7051