mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-27 09:46:06 +03:00
[GH-ISSUE #5775] [feature]: Support for SMTP OAuth2 (XOAUTH2) for Microsoft 365 SMTP #2257
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#2257
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @myeongkil on GitHub (Jan 16, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5775
Is there an existing issue for this?
Summary
Related to #4401 #5251
Hoppscotch only supports password-based SMTP today, which prevents integration with providers requiring OAuth2/XOAUTH2
Why should this be worked on?
Current Limitation
At the moment, Hoppscotch only supports password-based custom SMTP authentication.
This design assumes:
This approach works with legacy SMTP providers or local testing tools (MailCatcher, Mailpit),
but it cannot be used with modern enterprise mail providers.
ref. Microsoft 365 (Exchange Online) has deprecated and disabled SMTP Basic Authentication.
SMTP access now requires OAuth2 (XOAUTH2) with access tokens, not passwords.