Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

期望用户邮箱通知时只通知已验证的邮箱 #5722

Closed
guqing opened this issue Apr 16, 2024 · 0 comments · Fixed by #5905
Closed

期望用户邮箱通知时只通知已验证的邮箱 #5722

guqing opened this issue Apr 16, 2024 · 0 comments · Fixed by #5905
Assignees
Labels
area/core Issues or PRs related to the Halo Core kind/improvement Categorizes issue or PR as related to a improvement.
Milestone

Comments

@guqing
Copy link
Member

guqing commented Apr 16, 2024

Your current Halo version

2.14.0

Describe this feature

目前用户已经支持邮箱验证功能,通知功能在给用户发送邮件通知时应该只对已验证的邮箱地址发送邮件

Additional information

/kind improvement
/area core
/milestone 2.15.x
/assign

@f2c-ci-robot f2c-ci-robot bot added the kind/improvement Categorizes issue or PR as related to a improvement. label Apr 16, 2024
@f2c-ci-robot f2c-ci-robot bot added this to the 2.15.x milestone Apr 16, 2024
@f2c-ci-robot f2c-ci-robot bot added the area/core Issues or PRs related to the Halo Core label Apr 16, 2024
@ruibaby ruibaby modified the milestones: 2.15.x, 2.16.x May 7, 2024
f2c-ci-robot bot pushed a commit that referenced this issue May 20, 2024
…resses (#5905)

#### What type of PR is this?
/kind improvement
/area core
/milestone 2.16.x

#### What this PR does / why we need it:
邮件通知功能现在只向经过验证的邮箱地址发送通知匿名用户除外

#### Which issue(s) this PR fixes:
Fixes #5722

#### Does this PR introduce a user-facing change?
```release-note
邮件通知功能现在只向经过验证的邮箱地址发送通知匿名用户除外
```
@ruibaby ruibaby modified the milestones: 2.16.x, 2.16.0 May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/core Issues or PRs related to the Halo Core kind/improvement Categorizes issue or PR as related to a improvement.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants