Gitea: Allow commenting tickets via mail
It would be useful to be able to reply to email notified upon ticket activity.
This is more or less what's requested to Gogs via https://github.com/gogits/gogs/issues/2602#issuecomment-233976184
It could be some gitea readmail comand reading a message from stdin, letting system administrators configure an email address forwarded to the command (would be easy in unix world). Implies holding a database with identifiers for threads/users to match.
strk
All 14 comments
Not an easy task because multiple input ways have to be covered.
tboerger
on 24 Jan 2017
Hello,
Maybe the solution would be to add some parameter to access a pop3 mailbox and gitea will retrieve each 5 minutes the mailbox content. This way was already implemented in forum discurse.
Josue-T
on 15 Apr 2020
Or we could add smtp server to gitea :]
lafriks
on 15 Apr 2020
@lafriks We just need to check email via pop/IMAP protocol.
lunny
on 19 Apr 2020
The problem is how we recognize which email is a comment to which repository's which issue. We need make a rule.
lunny
on 19 Apr 2020
In-Reply-To or References header that matches an email that was sent from the issue? http://jkorpela.fi/headers.html
ptman
on 19 Apr 2020
It seems right. We can include a header in the email we sent. But when user reply to this email, if the header will be copied to the reply email?
lunny
on 19 Apr 2020
That's right. Here is the message in github email, may be we can try same style ...
Date: Sun, 19 Apr 2020 07:43:39 -0700 From: Lunny Xiao <[email protected]> Reply-To: go-gitea/gitea <[email protected]> To: go-gitea/gitea <[email protected]> Cc: Subscribed <[email protected]> Message-ID: <go-gitea/gitea/issues/745/[email protected]> In-Reply-To: <go-gitea/gitea/issues/[email protected]> References: <go-gitea/gitea/issues/[email protected]> Subject: Re: [go-gitea/gitea] Allow commenting tickets via mail (#745) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5e9c639bb9db_2ac03fa88d0cd9681698d"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: lunny X-GitHub-Recipient: a1012112796 X-GitHub-Reason: subscribed List-ID: go-gitea/gitea <gitea.go-gitea.github.com> List-Archive: https://github.com/go-gitea/gitea List-Post: <mailto:[email protected]> List-Unsubscribe: <mailto:unsub+AGBLDSVFHOXULGY25KN7O554VBCJXEVBNHHAYF6MYI@reply.github.com>, <https://github.com/notifications/unsubscribe/AGBLDSQ4RV7B75FDV4HYPQLRNMEZXANCNFSM4C5SGZ3A> X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: [email protected]
and it has a fast reply button, which I used now. I think It's also usefull.
------------------ 原始邮件 ------------------
发件人: "Lunny Xiao"<[email protected]>;
发送时间: 2020年4月19日(星期天) 晚上10:43
收件人: "go-gitea/gitea"<[email protected]>;
抄送: "Subscribed"<[email protected]>;
主题: Re: [go-gitea/gitea] Allow commenting tickets via mail (#745)
It seems right. We can include a header in the email we sent. But when user reply to this email, if the header will be copied to the reply email?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
a1012112796
on 19 Apr 2020
Here is my first time to try email reply in github, I found the commet published by email is more slow to show on ui than comment directly . so maybe github also did the same things which we thinking :)
a1012112796
on 19 Apr 2020
maybe we have send replies message now ...
https://github.com/go-gitea/gitea/blob/9f959ac0641821148e46d0899b74cc714c858879/services/mailer/mail.go#L249-L258
So maybe only need to add something to recive email 😊
@lunny
a1012112796
on 26 Apr 2020
A gitea commandline argument to "parse mail" would be enough for a
start. A system administrator would setup their favorite mechanism
to receive mail and would pipe the mail content to such new
commandline.
strk
on 27 Apr 2020
A
giteacommandline argument to "parse mail" would be enough for a
start. A system administrator would setup their favorite mechanism
to receive mail and would pipe the mail content to such new
commandline.
It's reasonble, But I think we can also add built-in IMAP suport to recive email . it will be more easily for user to use.Maybe we call choose one from them:
https://github.com/search?l=Go&q=IMAP&type=Repositories
a1012112796
on 27 Apr 2020
A
giteacommandline argument to "parse mail" would be enough for a
start. A system administrator would setup their favorite mechanism
to receive mail and would pipe the mail content to such new
commandline.
There's always the API...
guillep2k
on 28 Apr 2020
a1012112796
on 16 Sep 2020
Related issues
thehowl
·
3Comments
flozz
·
3Comments
jakimfett
·
3Comments
lunny
·
3Comments
ghost
·
3Comments
Most helpful comment
A
giteacommandline argument to "parse mail" would be enough for astart. A system administrator would setup their favorite mechanism
to receive mail and would pipe the mail content to such new
commandline.