-
Notifications
You must be signed in to change notification settings - Fork 17
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
Unable to send HTML emails #70
Comments
Seems like it might have to do with the email provider we're using? Maybe? We're using Sakura Internet as our email provider. And Sensu is using it to send emails to other accounts using Sakura email. If I send an HTML email from Gmail to a Sakura email account, the HTML styles show up. You can't see any HTML tags. If I use Sensu to send an email from a Sakura mail account to another Sakura mail account, the HTML styles do not show up and they display in plain text. However, if I use an email client to send an HTML Email from a Sakura mail account, the HTML styles do show up and you can't see any HTML tags. It's weird. |
Actually, it seems like it is a problem with Spark? Or at the very least I've only been able to reproduce the problem when using the Spark client for MacOS. |
Here is a raw version of the email being generated (I changed some names/ids to protect sensitive information)
|
sensu-backend version 6.7.2+ee, enterprise edition, build e0d4063f2671a83ef64938c0ac7d2f3bd30e0a8d, built 2022-05-11T21:42:19Z, built with go1.17.6
sensu-backend version 6.7.2+ee, enterprise edition, build e0d4063f2671a83ef64938c0ac7d2f3bd30e0a8d, built 2022-05-11T21:42:19Z, built with go1.17.6
1.2.2
sensu-backend is running on Ubuntu 20.04
sensu-agent is running on Windows Server 2019
I tried some simple HTML content, like so.
It successfully uses the template, but it is sent as plaintext.
I also tried copy/pasting the template that is available in the documentation, and that also resulted in just plain text.
The following is an example of what I'm receiving as an email.
The text was updated successfully, but these errors were encountered: