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

[Feature] Email to WeChat #82

Open
huan opened this issue Mar 20, 2020 · 2 comments
Open

[Feature] Email to WeChat #82

huan opened this issue Mar 20, 2020 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@huan
Copy link
Collaborator

huan commented Mar 20, 2020

The Problem

  1. We have dev@project.apache.org email list and but we do not check email very often.
  2. We want to see message cards in WeChat when we have new emails in our mail list.

The Solution

We can sync the email message to our WeChat group the same as GitHub Issue to WeChat.

Steps

  1. create an email address bot@oss.chat to receive emails
  2. add the bot@oss.chat to the specific email list, so that the bot can start receiving the emails
  3. setup on the OSSChat project so that the system gets to know we should send which email list to which WeChat group.

E.g. dev@doris.incubator.apache.org -> 43241234@chatroom

Related Projects

  1. Mailgun webhook to Slack integration
@huan
Copy link
Collaborator Author

huan commented Mar 20, 2020

We need an email box to store all the emails sent to bot@oss.chat address.

I'd like to suggest that create an email box named osschat-bot@kaiyuanshe.org for this feature. @zhuangbiaowei

@huan huan self-assigned this Mar 26, 2020
@huan huan added the enhancement New feature or request label Mar 27, 2020
@huan
Copy link
Collaborator Author

huan commented May 12, 2022

@tedliu1 We can track the email to wechat feature with this issue as you had mentioned yesterday.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant