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.

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

Configuration to add custom SMTP headers #28507

Open
Barbiero opened this issue Oct 23, 2020 · 8 comments
Open

Configuration to add custom SMTP headers #28507

Barbiero opened this issue Oct 23, 2020 · 8 comments
Labels
area/backend/config prio/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough interest in it. type/feature-request

Comments

@Barbiero
Copy link

What would you like to be added:

The ability to add custom SMTP headers to emails sent by Grafana

Why is this needed:

Certain SMTP providers support custom manipulation of emails according to SMTP headers. For example, Postmark allows enabling or disabling link tracking by setting the SMTP header X-PM-TrackLinks: None.

I believe this is an inconsequential addition that would benefit some use cases. An initial implementation could allow us to set this on grafana.ini with a simple additional_headers: [key]=[value].

@ivanahuckova ivanahuckova added this to Inbox in Backend Platform Backlog via automation Oct 23, 2020
@wbrowne wbrowne added the prio/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough interest in it. label Oct 26, 2020
@wbrowne
Copy link
Member

wbrowne commented Oct 26, 2020

Thanks for creating this issue @Barbiero. Unfortunately in order to add support for this in Grafana, we'd first like to see if there is a high demand for this feature.

In the meantime, perhaps a SMTP proxy could be used to support your particular use-case?

@wbrowne wbrowne removed this from Inbox in Backend Platform Backlog Oct 26, 2020
@Barbiero
Copy link
Author

That's a good idea, I'll look into it. Thanks!

For me in particular, this isn't high priority. The grafana emails are all internal within our organization so even if there's click tracking we don't really care that much, it just would be nice to have. I figured the possibility of additional headers would be interesting for other users as well.

@wbrowne
Copy link
Member

wbrowne commented Oct 26, 2020

Great! Thanks for the extra context.

Sounds great. We'll leave the issue here for the meantime in order to gauge priority.

Thanks again @Barbiero!

@eacherkan-aternity
Copy link

AWS's Simple Email Service also uses SMTP email headers for switching between configuration sets: https://docs.aws.amazon.com/ses/latest/dg/event-publishing-send-email.html#event-publishing-using-ses-headers

@melindam
Copy link

melindam commented Apr 4, 2022

This would have been nice to have, found out the external mail services need a header, and since we are in the cloud .. its required

  • Configure the Public Cloud server/system to use the following options including the mail header.
mail header: x-ComanyName-Azure: Yes
SMTP host: maild2.corpmailsvcs.com

@trauta
Copy link

trauta commented May 4, 2022

I am also interested in this feature since our mail servers need additional headers to in order to accept mails from our Grafana installations.

Copy link
Contributor

This issue has been automatically marked as stale because it has not had activity in the last year. It will be closed in 30 days if no further activity occurs. Please feel free to leave a comment if you believe the issue is still relevant. Thank you for your contributions!

@github-actions github-actions bot added the stale Issue with no recent activity label Jan 21, 2024
@Tonic8
Copy link

Tonic8 commented Feb 9, 2024

Hello

i'm really interested

in my case it's mandatory to tag the sensitivity level of the header mail, the sensivity like public/internal/confidential. to allow mail archiving tools to filter/store/block maild depending of the sensitivity level.

REquired because we use Microsoft AIP.

@github-actions github-actions bot removed the stale Issue with no recent activity label Feb 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/backend/config prio/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough interest in it. type/feature-request
Projects
None yet
Development

No branches or pull requests

7 participants