Allow commenting tickets via mail #275

@Josue-T commented on GitHub (Apr 15, 2020):

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 commented on GitHub (Apr 15, 2020): 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.

GiteaMirror commented

@lafriks commented on GitHub (Apr 15, 2020):

Or we could add smtp server to gitea :]

@lafriks commented on GitHub (Apr 15, 2020): Or we could add smtp server to gitea :]

GiteaMirror commented

@lunny commented on GitHub (Apr 19, 2020):

@lafriks We just need to check email via pop/IMAP protocol.

@lunny commented on GitHub (Apr 19, 2020): @lafriks We just need to check email via pop/IMAP protocol.

GiteaMirror commented

@lunny commented on GitHub (Apr 19, 2020):

The problem is how we recognize which email is a comment to which repository's which issue. We need make a rule.

@lunny commented on GitHub (Apr 19, 2020): The problem is how we recognize which email is a comment to which repository's which issue. We need make a rule.

GiteaMirror commented

@ptman commented on GitHub (Apr 19, 2020):

In-Reply-To or References header that matches an email that was sent from the issue? http://jkorpela.fi/headers.html

@ptman commented on GitHub (Apr 19, 2020): In-Reply-To or References header that matches an email that was sent from the issue? http://jkorpela.fi/headers.html

GiteaMirror commented

@lunny commented on GitHub (Apr 19, 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 commented on GitHub (Apr 19, 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?

GiteaMirror commented

@a1012112796 commented on GitHub (Apr 19, 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 <notifications@github.com&gt; Reply-To: go-gitea/gitea <reply@reply.github.com&gt; To: go-gitea/gitea <gitea@noreply.github.com&gt; Cc: Subscribed <subscribed@noreply.github.com&gt; Message-ID: <go-gitea/gitea/issues/745/616150955@github.com&gt; In-Reply-To: <go-gitea/gitea/issues/745@github.com&gt; References: <go-gitea/gitea/issues/745@github.com&gt; 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&gt; List-Archive: https://github.com/go-gitea/gitea List-Post: <mailto:reply@reply.github.com&gt; List-Unsubscribe: <mailto:unsub+AGBLDSVFHOXULGY25KN7O554VBCJXEVBNHHAYF6MYI@reply.github.com&gt;,  <https://github.com/notifications/unsubscribe/AGBLDSQ4RV7B75FDV4HYPQLRNMEZXANCNFSM4C5SGZ3A&gt; X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: 1012112796@qq.com

and it has a fast reply button, which I used now. I think It's also usefull.

------------------ 原始邮件 ------------------
发件人: "Lunny Xiao"<notifications@github.com>;
发送时间: 2020年4月19日(星期天) 晚上10:43
收件人: "go-gitea/gitea"<gitea@noreply.github.com>;
抄送: "Subscribed"<subscribed@noreply.github.com>;
主题: 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 commented on GitHub (Apr 19, 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 <notifications@github.com> Reply-To: go-gitea/gitea <reply@reply.github.com> To: go-gitea/gitea <gitea@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Message-ID: <go-gitea/gitea/issues/745/616150955@github.com> In-Reply-To: <go-gitea/gitea/issues/745@github.com> References: <go-gitea/gitea/issues/745@github.com> 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:reply@reply.github.com> List-Unsubscribe: <mailto:unsub+AGBLDSVFHOXULGY25KN7O554VBCJXEVBNHHAYF6MYI@reply.github.com>, <https://github.com/notifications/unsubscribe/AGBLDSQ4RV7B75FDV4HYPQLRNMEZXANCNFSM4C5SGZ3A> X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: 1012112796@qq.com ``` and it has a fast reply button, which I used now. I think It's also usefull. ------------------ 原始邮件 ------------------ 发件人: "Lunny Xiao"<notifications@github.com>; 发送时间: 2020年4月19日(星期天) 晚上10:43 收件人: "go-gitea/gitea"<gitea@noreply.github.com>; 抄送: "Subscribed"<subscribed@noreply.github.com>; 主题: 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.

GiteaMirror commented

@a1012112796 commented on GitHub (Apr 19, 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 commented on GitHub (Apr 19, 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 :)

GiteaMirror commented

@a1012112796 commented on GitHub (Apr 26, 2020):

maybe we have send replies message now ...
9f959ac064/services/mailer/mail.go (L249-L258)
So maybe only need to add something to recive email 😊
@lunny

@a1012112796 commented on GitHub (Apr 26, 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

GiteaMirror commented

@strk commented on GitHub (Apr 27, 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 commented on GitHub (Apr 27, 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.

GiteaMirror commented

@a1012112796 commented on GitHub (Apr 27, 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.

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 commented on GitHub (Apr 27, 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. 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

GiteaMirror commented

@guillep2k commented on GitHub (Apr 28, 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.

There's always the API...

@guillep2k commented on GitHub (Apr 28, 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. There's always the API...

GiteaMirror commented