langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Support SMTP OAuth 2.0 Authentication (Microsoft Exchange Compatibility) #14724

New Issue
Closed
opened 2026-02-21 19:18:29 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:18:29 -05:00
Owner
Copy Link
Copy Source

Originally created by @laipz8200 on GitHub (Jun 19, 2025).

Originally assigned to: @laipz8200 on GitHub.

Self Checks

  • 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.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Microsoft will retire support for SMTP Basic Authentication in September 2025, specifically for the Client Submission protocol (SMTP AUTH). This change directly affects all users who rely on Microsoft Exchange mailboxes integrated via Basic Auth for sending emails.

To maintain compatibility and improve overall security, we need to implement support for SMTP OAuth 2.0, with priority given to Microsoft Exchange email compatibility.

Impact:

  • Users with Microsoft Exchange accounts will no longer be able to use SMTP Basic Auth to send emails once Microsoft disables it.
  • This will disrupt email integration features that depend on SMTP AUTH, potentially affecting critical business workflows.

Requirements:

  • Implement support for SMTP using OAuth 2.0 authentication, compatible with Microsoft OAuth 2.0 endpoints.
  • Prioritize Microsoft Exchange support in implementation and testing.
  • Provide configuration guidelines and usage documentation for administrators and users.

Reference:

Microsoft announcement:
https://techcommunity.microsoft.com/blog/exchange/exchange-online-to-retire-basic-auth-for-client-submission-smtp-auth/4114750

“Exchange Online will permanently remove support for Basic authentication with Client Submission (SMTP AUTH) in September 2025… any clients or apps connecting using Basic auth will receive: 550 5.7.30 Basic authentication is not supported for Client Submission”

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @laipz8200 on GitHub (Jun 19, 2025). Originally assigned to: @laipz8200 on GitHub. ### Self Checks - [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. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. Microsoft will retire support for SMTP Basic Authentication in **September 2025**, specifically for the Client Submission protocol (SMTP AUTH). This change directly affects all users who rely on Microsoft Exchange mailboxes integrated via Basic Auth for sending emails. To maintain compatibility and improve overall security, we need to implement support for **SMTP OAuth 2.0**, with priority given to Microsoft Exchange email compatibility. --- **Impact:** - Users with Microsoft Exchange accounts will **no longer be able to use SMTP Basic Auth** to send emails once Microsoft disables it. - This will disrupt email integration features that depend on SMTP AUTH, potentially affecting critical business workflows. --- **Requirements:** - Implement support for **SMTP using OAuth 2.0 authentication**, compatible with Microsoft OAuth 2.0 endpoints. - Prioritize Microsoft Exchange support in implementation and testing. - Provide configuration guidelines and usage documentation for administrators and users. --- **Reference:** Microsoft announcement: https://techcommunity.microsoft.com/blog/exchange/exchange-online-to-retire-basic-auth-for-client-submission-smtp-auth/4114750 > “Exchange Online will permanently remove support for Basic authentication with Client Submission (SMTP AUTH) in **September 2025**… any clients or apps connecting using Basic auth will receive: `550 5.7.30 Basic authentication is not supported for Client Submission`” ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 19:18:29 -05:00
yindo closed this issue 2026-02-21 19:18:29 -05:00
yindo commented 2026-02-21 19:18:29 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi, @laipz8200. I'm Dosu (https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested adding SMTP OAuth 2.0 authentication support for Microsoft Exchange.
  • This is important because Microsoft Exchange will retire SMTP Basic Authentication by September 2025.
  • The feature is needed to prevent disruptions in sending emails through Exchange accounts.
  • You expressed willingness to contribute to the implementation.
  • There has been no further activity or comments on this issue.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of Dify by commenting here.
  • If I do not hear back within 15 days, this issue will be automatically closed.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 18, 2025): Hi, @laipz8200. I'm Dosu (https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested adding SMTP OAuth 2.0 authentication support for Microsoft Exchange. - This is important because Microsoft Exchange will retire SMTP Basic Authentication by September 2025. - The feature is needed to prevent disruptions in sending emails through Exchange accounts. - You expressed willingness to contribute to the implementation. - There has been no further activity or comments on this issue. **Next Steps:** - Please let me know if this issue is still relevant to the latest version of Dify by commenting here. - If I do not hear back within 15 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
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 💪 enhancement
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#14724
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?