Allow mailer Reply-To override per project

[gradha]

The mailer FROM configuration option I found in the cheat sheet is very useful. Would be really good if this FROM field could be customized per project to have different return addresses matching the appropriate mailing lists.

[unknwon]

Thanks your feedback!

Why do you need this per project? Because issue-related email's From will eventually be the person who triggers the email notification. Seems nothing much useful places left.

[strk]

I think in the long run the "From" should point to a temporary ad-hoc address setup to handle commenting by mail (see also #2602)

[unknwon]

@strk I'm not pro on emailing, but I think reply-to-comment is the email header reply-to not from?

[strk]

On Mon, Jul 25, 2016 at 09:26:26AM -0700, 无闻 wrote:

@strk I'm not pro on emailing, but I think reply-to-comment is the email header reply-to not from?

In presence of a Reply-To, yes, it takes precedence.
Github does use Reply-To for handling the by-mail replies.

[gradha]

As admin of a gogs instance I did set the FROM field to a separate personal email I didn't use. When users started replying to notifications those were lost until I checked that account. This meant that development conversation stalled for no apparent reason.

Not being related to those projects, setting repos for separate organizations would place an extra burden on me to deal with email forwarding in such situations, which then I'd have to look up these users in the database to send the email to the appropriate group.

Setting a From or Reply-To header for these groups would alleviate this administration burden.

[unknwon]

@gradha I think what you need is Allow mailer Reply-To override per project instead of From?

[gradha]

If the effect is the same, yes.