langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

[email plugin] send_mail_batch.py does not use sender_address, causing SES integration to fail #244

New Issue
Closed
opened 2026-02-16 10:18:34 -05:00 by yindo · 3 comments
yindo commented 2026-02-16 10:18:34 -05:00
Owner
Copy Link
Copy Source

Originally created by @sanokenichiro-alsi on GitHub (Apr 30, 2025).

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 Dify issues & Dify Official Plugins, 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

1.3.1

Plugin version

0.0.7

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Hello,
I have never developed OSS application so I want somebody to fix this issue.
This is email plugin issue.

In send_mail.py, the sender email address used for header (From:) is correctly taken from the sender_address credential, falling back to email_account. However, send_mail_batch.py only uses email_account, which often holds a non-email SMTP username (e.g., for Amazon SES). This causes the validation check for email format to fail with:

"Invalid parameter userid, the sender is not a mailbox"

Suggested fix :
Use sender_address = self.runtime.credentials.get("sender_address", sender) or sender in send_mail_batch.py just like in send_mail.py, and pass it to SendEmailToolParameters.

Best regards,
Sano

✔️ Error log

No response

Originally created by @sanokenichiro-alsi on GitHub (Apr 30, 2025). ### 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 [Dify issues](https://github.com/langgenius/dify/issues) & [Dify Official Plugins](https://github.com/langgenius/dify-official-plugins/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 1.3.1 ### Plugin version 0.0.7 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Hello, I have never developed OSS application so I want somebody to fix this issue. This is email plugin issue. In send_mail.py, the sender email address used for header (From:) is correctly taken from the sender_address credential, falling back to email_account. However, send_mail_batch.py only uses email_account, which often holds a non-email SMTP username (e.g., for Amazon SES). This causes the validation check for email format to fail with: "Invalid parameter userid, the sender is not a mailbox" Suggested fix : Use sender_address = self.runtime.credentials.get("sender_address", sender) or sender in send_mail_batch.py just like in send_mail.py, and pass it to SendEmailToolParameters. Best regards, Sano ### ✔️ Error log _No response_
yindo added the bug label 2026-02-16 10:18:34 -05:00
yindo closed this issue 2026-02-16 10:18:34 -05:00
yindo commented 2026-02-16 10:18:35 -05:00
Author
Owner
Copy Link
Copy Source

@adithya-adee commented on GitHub (May 19, 2025):

Hey!! @sanokenichiro-alsi
I would love to work on this issue and fix the bug. I would try to fix this bug & make sure it works perfectly.
If this issue is still open, can you assign me this?

@adithya-adee commented on GitHub (May 19, 2025): Hey!! @sanokenichiro-alsi I would love to work on this issue and fix the bug. I would try to fix this bug & make sure it works perfectly. If this issue is still open, can you assign me this?
yindo commented 2026-02-16 10:18:35 -05:00
Author
Owner
Copy Link
Copy Source

@sanokenichiro-alsi commented on GitHub (May 31, 2025):

@adithya-adee Thank you so much.
I don't have permission to assign this issue to you.

@sanokenichiro-alsi commented on GitHub (May 31, 2025): @adithya-adee Thank you so much. I don't have permission to assign this issue to you.
yindo commented 2026-02-16 10:18:35 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 19, 2025):

Hi, @sanokenichiro-alsi. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported a bug where send_mail_batch.py does not use the sender_address credential, causing Amazon SES integration to fail.
  • You suggested updating send_mail_batch.py to use sender_address similarly to send_mail.py.
  • Contributor adithya-adee expressed interest in fixing the bug but you mentioned lacking permission to assign the issue.
  • No fix has been implemented yet.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here.
  • If I do not hear back within 5 days, this issue will be automatically closed.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 19, 2025): Hi, @sanokenichiro-alsi. I'm [Dosu](https://dosu.dev), and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported a bug where `send_mail_batch.py` does not use the `sender_address` credential, causing Amazon SES integration to fail. - You suggested updating `send_mail_batch.py` to use `sender_address` similarly to `send_mail.py`. - Contributor adithya-adee expressed interest in fixing the bug but you mentioned lacking permission to assign the issue. - No fix has been implemented yet. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here. - If I do not hear back within 5 days, this issue will be automatically closed. Thank you for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#244
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?