Option for email notifications to use common sender email address #8926

New Issue

GiteaMirror · 2025-11-02T08:23:20-06:00

GiteaMirror commented

2025-11-02 08:23:20 -06:00

Originally created by @Andrew-Staves-Activ on GitHub (May 6, 2022).

Feature Description

Gitea currently sends notification emails with the From header set to the email address of the user who triggered the notification - e.g. the user who created an issue. It would be useful if there was an option to disable this so that the email notifications would instead be sent from the same email address that's used for general emails - the one in ENVELOPE_FROM / FROM.

Currently, I can't use the email account that I should be using because it is only allowed to send email as one generic address (like no-reply@wherever.com) and is not allowed to send email as arbitrary users.

Screenshots

No response

Originally created by @Andrew-Staves-Activ on GitHub (May 6, 2022). ### Feature Description Gitea currently sends notification emails with the From header set to the email address of the user who triggered the notification - e.g. the user who created an issue. It would be useful if there was an option to disable this so that the email notifications would instead be sent from the same email address that's used for general emails - the one in `ENVELOPE_FROM` / `FROM`. Currently, I can't use the email account that I should be using because it is only allowed to send email as one generic address (like no-reply@wherever.com) and is not allowed to send email as arbitrary users. ### Screenshots _No response_

GiteaMirror added the type/proposal type/feature labels 2025-11-02 08:23:20 -06:00

GiteaMirror commented

2025-11-02 08:23:20 -06:00

@aleb commented on GitHub (May 10, 2024):

"currently" is used incorrectly in the first paragraph.

Also the title, maybe:
"Support sending notification emails as the person who made the change"

@aleb commented on GitHub (May 10, 2024): "currently" is used incorrectly in the first paragraph. Also the title, maybe: "Support sending notification emails as the person who made the change"

GiteaMirror commented

2025-11-02 08:23:20 -06:00

@Andrew-Staves-Activ commented on GitHub (May 10, 2024):

"currently" is used incorrectly in the first paragraph.

Also the title, maybe: "Support sending notification emails as the person who made the change"

This issue was created quite some time ago - specifically the 6th of May, 2022!
I believe that my description is (or, at least, was) accurate - it reflects what was seen in the Gitea instance I was using at the time I created the issue. I imagine that version is probably considerably out-of-date by now. I perhaps should have specified the version that was being used at the time and/or began "Currently our Gitea instance" (etc.).

I have admittedly not tested the notification email behaviour in a newer version of Gitea since creating this issue (priorities have changed, Gitea is being used less etc.).

To (hopefully) clarify, what you appear to be suggesting in your title is - or, at least, was - the behaviour at the time of creating this issue. The desired functionality was the opposite - i.e., to be able to not have the email sent as the person who made the change and instead send as the common sender email address that is used for non-notification emails (regardless of who made a change or otherwise triggered a notification).

I'd be interested to know if the ability to send notification emails as the common sender email address does exist in a version of Gitea that was released since I originally created this issue though, thanks!

@Andrew-Staves-Activ commented on GitHub (May 10, 2024): > "currently" is used incorrectly in the first paragraph. > > Also the title, maybe: "Support sending notification emails as the person who made the change" This issue was created quite some time ago - specifically the 6th of May, 2022! I believe that my description is (or, at least, was) accurate - it reflects what was seen in the Gitea instance I was using at the time I created the issue. I imagine that version is probably considerably out-of-date by now. I perhaps should have specified the version that was being used at the time and/or began "Currently our Gitea instance" (etc.). I have admittedly not tested the notification email behaviour in a newer version of Gitea since creating this issue (priorities have changed, Gitea is being used less etc.). To (hopefully) clarify, what you appear to be suggesting in your title is - or, at least, was - the behaviour at the time of creating this issue. The desired functionality was the opposite - i.e., to be able to _not_ have the email sent as the person who made the change and instead send as the common sender email address that is used for non-notification emails (regardless of who made a change or otherwise triggered a notification). I'd be interested to know if the ability to send notification emails as the common sender email address does exist in a version of Gitea that was released since I originally created this issue though, thanks!

GiteaMirror commented

2025-11-02 08:23:21 -06:00

@aleb commented on GitHub (May 11, 2024):

Currently the notification emails are sent from a unique email address. (In my team we want the opposite)

@aleb commented on GitHub (May 11, 2024): Currently the notification emails are sent from a unique email address. (In my team we want the opposite)

GiteaMirror commented

2025-11-02 08:23:21 -06:00

@aleb commented on GitHub (May 11, 2024):

The original description of the issue is confusing, the two paragraphs are contradicting each other.

@aleb commented on GitHub (May 11, 2024): The original description of the issue is confusing, the two paragraphs are contradicting each other.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#8926