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.

Sign up for GitHub

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

Jump to bottom

Create issue via email #6226

Open
MartinDelille opened this issue Mar 2, 2019 · 2 comments
Open

Create issue via email #6226

MartinDelille opened this issue Mar 2, 2019 · 2 comments
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@MartinDelille
Copy link
Contributor

Another Gitlab EE feature that would be nice to have in Gitea: https://docs.gitlab.com/ee/administration/incoming_email.html

This feature is blocking the service desk feature: #6219
@MartinDelille MartinDelille changed the title Create issue by email Create issue via email Mar 2, 2019
@MartinDelille MartinDelille mentioned this issue Mar 2, 2019
Merged
@lunny lunny added type/proposal The new feature has not been accepted yet but needs to be discussed first. type/feature Completely new functionality. Can only be merged if feature freeze is not active. labels Mar 2, 2019
@MOZGIII
Copy link

MOZGIII commented Mar 5, 2019

I'd deploy is as a separate unit, and just create a support for creaing issues via API. Rationale is there can be a lot of sources to create an issue, and coupling the gitea with email recieving functionality seems unnesessarily specific. Consuming emails is a tricky thing, and it worth being a separate unit - maybe there is something we could utilize already.
Altough, I'm new here and I don't know how things are done.

@KN4CK3R KN4CK3R mentioned this issue Dec 7, 2022
Merged
lunny added a commit that referenced this issue Jan 14, 2023
@KN4CK3R @silverwind @lunny
Add support for incoming emails (#22056)
fc037b4 
closes #13585
fixes #9067
fixes #2386
ref #6226
ref #6219
fixes #745

This PR adds support to process incoming emails to perform actions.
Currently I added handling of replies and unsubscribing from
issues/pulls. In contrast to #13585 the IMAP IDLE command is used
instead of polling which results (in my opinion 😉) in cleaner code.

Procedure:
- When sending an issue/pull reply email, a token is generated which is
present in the Reply-To and References header.
- IMAP IDLE waits until a new email arrives
- The token tells which action should be performed

A possible signature and/or reply gets stripped from the content.

I added a new service to the drone pipeline to test the receiving of
incoming mails. If we keep this in, we may test our outgoing emails too
in future.

Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
@sclu1034
Copy link

sclu1034 commented Aug 5, 2024

As can be seen in the timeline, Gitea does now handle incoming emails. Though currently with the restriction "existing users replying to existing issues".

But it does mean it's now a much smaller step towards also accepting messages from addresses that don't belong to a registered user, and to have a repository-wide address that creates new issues/pull requests when messaged.

Running a single-user instance where I would like to be able to accept contributions without having to deal with registered users, I would love to see this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@lunny @MOZGIII @MartinDelille @sclu1034