starred/ntfy
1
0
Fork 0
mirror of https://github.com/binwiederhier/ntfy.git synced 2026-05-09 08:26:00 +02:00
Code Issues 368 Projects Packages Wiki Activity

[GH-ISSUE #690] html-only emails allow publishing #508

New issue
Closed
opened 2026-05-07 00:24:55 +02:00 by BreizhHardware · 13 comments
BreizhHardware commented 2026-05-07 00:24:55 +02:00
Owner
Copy link

Originally created by @teastrainer on GitHub (Mar 30, 2023).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/690

Emails can be used to publish messages via ntfy. But html-only mails are rejected with the following error message "554 5.0.0 Error: transaction failed, blame it on the weather: unsupported content type (in reply to end of DATA command)"

That's obviously for security reasons, which are understandable (potentially active / malicious code hidden in the text).

IIRC, emails consisting of text and html text are processed by ignoring the html part.

But sometimes we cannot change the structure of an email, especially if we want to use emails from home servers, home automation etc. Fritz Box for example can be used for email alerts, but sends html-only mails.

I think, there could be two ways to solve this problem:

a) fall back solution (as for emails consisting of text only and html-text):
Ignore or delete html part, meaning: delete / forget the body text completely. Then only the subject would be left for additional information. This would be completely acceptable to me. The text could be replaced by a warning that it has been removed (to avoid too many questions as to why this was done).

b) remove html tags with the help of regex.
This could be done by a (multiline-) search for "(?s)<.*?>" and replacing it with nothing.

That would be an operation with a sledgehammer, as the text is not preserved completely, especially references / links are removed, too. But this is quite acceptable for me. I'll attach the source code of an email from my fritz box before and after processing (in geany text editor)

1 email source text for test with ntfy.txt
2 email source text for test with ntfy after processing with regex.txt

Originally created by @teastrainer on GitHub (Mar 30, 2023). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/690 Emails can be used to publish messages via ntfy. But html-only mails are rejected with the following error message "554 5.0.0 Error: transaction failed, blame it on the weather: unsupported content type (in reply to end of DATA command)" That's obviously for security reasons, which are understandable (potentially active / malicious code hidden in the text). IIRC, emails consisting of text and html text are processed by ignoring the html part. But sometimes we cannot change the structure of an email, especially if we want to use emails from home servers, home automation etc. Fritz Box for example can be used for email alerts, but sends html-only mails. I think, there could be two ways to solve this problem: a) fall back solution (as for emails consisting of text only and html-text): Ignore or delete html part, meaning: delete / forget the body text completely. Then only the subject would be left for additional information. This would be completely acceptable to me. The text could be replaced by a warning that it has been removed (to avoid too many questions as to why this was done). b) remove html tags with the help of regex. This could be done by a (multiline-) search for "(?s)<.*?>" and replacing it with nothing. That would be an operation with a sledgehammer, as the text is not preserved completely, especially references / links are removed, too. But this is quite acceptable for me. I'll attach the source code of an email from my fritz box before and after processing (in geany text editor) [1 email source text for test with ntfy.txt](https://github.com/binwiederhier/ntfy/files/11116977/1.email.source.text.for.test.with.ntfy.txt) [2 email source text for test with ntfy after processing with regex.txt](https://github.com/binwiederhier/ntfy/files/11116978/2.email.source.text.for.test.with.ntfy.after.processing.with.regex.txt)
BreizhHardware 2026-05-07 00:24:55 +02:00
BreizhHardware commented 2026-05-07 00:24:56 +02:00
Author
Owner
Copy link

@binwiederhier commented on GitHub (Mar 31, 2023):

I researched and dabbled with it a bit, and I even had an (infuriatingly bad) conversation with ChatGPT about it (ha! the new world!), and I have decided that there is no safe and easy way to strip HTML tags using regex or other simple means. ChatGPT gave me a few examples showing how stripping with regex could be dangerous.

Anyway, I looked at bluemonday, and it seems that it doesn't pull in a giant chain of other dependencies, so I think it'll be fine to use it for HTML tag stripping.

I'd be happy to accept PRs and/or may do it myself some day when I am bored.

One important note about potential PRs: I do think we should prefer text/plain emails over text/html+stripping, which will change the parsing logic a little.

<!-- gh-comment-id:1491946203 --> @binwiederhier commented on GitHub (Mar 31, 2023): I researched and dabbled with it a bit, and I even had an (infuriatingly bad) conversation with ChatGPT about it (ha! the new world!), and I have decided that there is no safe and easy way to strip HTML tags using regex or other simple means. ChatGPT gave me a few examples showing how stripping with regex could be dangerous. Anyway, I looked at [bluemonday](https://github.com/microcosm-cc/bluemonday), and it seems that it doesn't pull in a giant chain of other dependencies, so I think it'll be fine to use it for HTML tag stripping. I'd be happy to accept PRs and/or may do it myself some day when I am bored. One important note about potential PRs: I do think we should prefer text/plain emails over text/html+stripping, which will change the parsing logic a little.
BreizhHardware commented 2026-05-07 00:24:56 +02:00
Author
Owner
Copy link

@teastrainer commented on GitHub (Mar 31, 2023):

I'm fine with it. What about the first option - just ignore / delete body text? Implementation of html tag stripping could then be done later.

<!-- gh-comment-id:1491982583 --> @teastrainer commented on GitHub (Mar 31, 2023): I'm fine with it. What about the first option - just ignore / delete body text? Implementation of html tag stripping could then be done later.
BreizhHardware commented 2026-05-07 00:24:56 +02:00
Author
Owner
Copy link

@binwiederhier commented on GitHub (Apr 2, 2023):

I have experimented with bluemonday and a few html emails and the results are absolutely terrible. Even with post processing, the result looks something like this:

	+=
        	            	+                        =20
        	            	+                                                                           =
        	            	+                        =20
        	            	+                                                                           =
        	            	+                        =20
        	            	+                                                                           =
        	            	+                        =20
        	            	+                                                                           =
        	            	+                        =20
        	            	+                                                                           =
        	            	+                        =20
        	            	+                                                                           =
        	            	+                        =20
        	            	+                                                                           =
        	            	+                        =20
        	            	+
        	            	+                       =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=
        	            	+=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C   
        	            	+
        	            	+  =20
        	            	+  =20
        	            	+  =20
        	            	+  =20
        	            	+  =20
        	            	+  =20
        	            	+  =20
        	            	+  =20
        	            	+  =20
        	            	+  =20
        	            	+  =20
        	            	+  =20
        	            	+
        	            	+=09 
        	            	+=09=09=09     
        	            	+=09 
        	            	+=09 
        	            	+=09=09  Dear Philipp,
        	            	+=09=09   
        	            	+=09=09
        	            	+=09=09
        	            	+=09=09We=E2=80=99re reaching out to you because you haven=E2=80=99t finishe=
        	            	+d filing your tax return with Turbotax. You can complete this by following =
        	            	+these instructions:=20
        	            	+

Not sure if this is better than having nothing at all.

<!-- gh-comment-id:1493340113 --> @binwiederhier commented on GitHub (Apr 2, 2023): I have experimented with bluemonday and a few html emails and the results are absolutely terrible. Even with post processing, the result looks something like this: ``` += + =20 + = + =20 + = + =20 + = + =20 + = + =20 + = + =20 + = + =20 + = + =20 + + =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2= +=80=8C =E2=80=8C =E2=80=8C =E2=80=8C =E2=80=8C  + + =20 + =20 + =20 + =20 + =20 + =20 + =20 + =20 + =20 + =20 + =20 + =20 + +=09 +=09=09=09 +=09 +=09 +=09=09 Dear Philipp, +=09=09   +=09=09 +=09=09 +=09=09We=E2=80=99re reaching out to you because you haven=E2=80=99t finishe= +d filing your tax return with Turbotax. You can complete this by following = +these instructions:=20 + ``` Not sure if this is better than having nothing at all.
BreizhHardware commented 2026-05-07 00:24:56 +02:00
Author
Owner
Copy link

@binwiederhier commented on GitHub (Apr 2, 2023):

See for yourself: https://github.com/binwiederhier/ntfy/pull/693.

Your demo email translates to this after my post-processing (ignore the " +" at the beginning of the lines):

        	            	+&lt;=21DOCTYPE html&gt;
        	            	+
        	            	+headertext of table
        	            	+
        	            	+&#34; Very important information about a change in your
        	            	+home automation setup 
        	            	+
        	            	+Now the light is on
        	            	+
        	            	+If you don&#39;t want to recieve this message anymore, stop the push
        	            	+ services in your  FRITZ=21Box =2E 
        	            	+Here you can see the active push services: &#34;System &gt; Push Service&#34;=2E
        	            	+
        	            	+This mail has ben sent by your  FRITZ=21Box  automatically=2E
<!-- gh-comment-id:1493403755 --> @binwiederhier commented on GitHub (Apr 2, 2023): See for yourself: https://github.com/binwiederhier/ntfy/pull/693. Your demo email translates to this after my post-processing (ignore the " +" at the beginning of the lines): ``` +&lt;=21DOCTYPE html&gt; + +headertext of table + +&#34; Very important information about a change in your +home automation setup + +Now the light is on + +If you don&#39;t want to recieve this message anymore, stop the push + services in your FRITZ=21Box =2E +Here you can see the active push services: &#34;System &gt; Push Service&#34;=2E + +This mail has ben sent by your FRITZ=21Box automatically=2E ```
BreizhHardware commented 2026-05-07 00:24:56 +02:00
Author
Owner
Copy link

@teastrainer commented on GitHub (Apr 7, 2023):

One of the problems seems to be that (at least in my example) the charset is utf-8 but the "Content-Transfer-Encoding: quoted-printable"

As bluemonday seems not to support such encoding, it may be necessary to convert the text to a "clean / full" utf-8 version before processing. E.g. FRITZ=21Box should be converted to FRITZ!Box

And I'm wondering about new characters for the processing of my text. In my example the original text <=21DOCTYPE html> is converted to &lt;=21DOCTYPE #html&gt;. So bluemonday replaces the characters < and > with &lt; and &gt; - which looks strange.

Maybe this can help: How to get a quoted printable string in golang

But I see, converting and sanitizing of html is difficult... As I said before I could live with the complete deletion of body text (if it's html-only).

<!-- gh-comment-id:1500264347 --> @teastrainer commented on GitHub (Apr 7, 2023): One of the problems seems to be that (at least in my example) the charset is utf-8 but the "Content-Transfer-Encoding: quoted-printable" As bluemonday seems not to support such encoding, it may be necessary to convert the text to a "clean / full" utf-8 version before processing. E.g. FRITZ=21Box should be converted to FRITZ!Box And I'm wondering about new characters for the processing of my text. In my example the original text `<=21DOCTYPE html>` is converted to `&lt;=21DOCTYPE #html&gt;`. So bluemonday replaces the characters `<` and `>` with `&lt;` and `&gt;` - which looks strange. Maybe this can help: [How to get a quoted printable string in golang](https://stackoverflow.com/questions/47299375/how-to-get-a-quoted-printable-string-in-golang) But I see, converting and sanitizing of html is difficult... As I said before I could live with the complete deletion of body text (if it's html-only).
BreizhHardware commented 2026-05-07 00:24:57 +02:00
Author
Owner
Copy link

@binwiederhier commented on GitHub (Apr 10, 2023):

quoted-printable is transparently stripped out by Go before, so it should not ever be visible by the reader. See https://pkg.go.dev/mime/multipart#Reader.NextPart --

As a special case, if the "Content-Transfer-Encoding" header has a value of "quoted-printable", that header is instead hidden and the body is transparently decoded during Read calls.

It is odd that the <=21DOCTYPE html> is not properly stripped out though. Not sure what's happening.

But I see, converting and sanitizing of html is difficult... As I said before I could live with the complete deletion of body text (if it's html-only).

That seems like a possibility. I may dabble with it a little more, and if I can't get anything good out, I'll do the title thing.

<!-- gh-comment-id:1502127798 --> @binwiederhier commented on GitHub (Apr 10, 2023): quoted-printable is transparently stripped out by Go before, so it should not ever be visible by the reader. See https://pkg.go.dev/mime/multipart#Reader.NextPart -- > As a special case, if the "Content-Transfer-Encoding" header has a value of "quoted-printable", that header is instead hidden and the body is transparently decoded during Read calls. It is odd that the `<=21DOCTYPE html>` is not properly stripped out though. Not sure what's happening. > But I see, converting and sanitizing of html is difficult... As I said before I could live with the complete deletion of body text (if it's html-only). That seems like a possibility. I may dabble with it a little more, and if I can't get anything good out, I'll do the title thing.
BreizhHardware commented 2026-05-07 00:24:57 +02:00
Author
Owner
Copy link

@teastrainer commented on GitHub (Apr 12, 2023):

Are you sure, bluemonday does detect the content-transfer-encoding (at all)? In my example, none of the quoted-printable codes is correctly decoded. Maybe there should be a dedicated "header" (format / tag / declaration) which is missing (at least) in my example.

<!-- gh-comment-id:1506051995 --> @teastrainer commented on GitHub (Apr 12, 2023): Are you sure, bluemonday does detect the content-transfer-encoding (at all)? In my example, none of the quoted-printable codes is correctly decoded. Maybe there should be a dedicated "header" (format / tag / declaration) which is missing (at least) in my example.
BreizhHardware commented 2026-05-07 00:24:57 +02:00
Author
Owner
Copy link

@Robert-litts commented on GitHub (Apr 13, 2023):

Hi! I just wanted to add to this with my use-case for HTML e-mails and Ntfy. I have been working to convert every conceivable device in my home to use Ntfy as my primary notification service. Unfortunately, several items still rely 100% on e-mail notification as their "only" form of notifications, so the SMTP aspect of Ntfy has been a lifesaver (thanks for all the troubleshooting we did over the past few months in Discord & in quickly tackling #610 !)

The latest one I am trying to work on is my Synology NAS which has e-mail notifications, but use HTML formatted messages and therefore receive the "554 5.0.0 Error: transaction failed, blame it on the weather: unsupported content type" error. I know this was discussed/closed in #623 , but saw this issue/WIP PR #693 and wanted to add the code that I receive from Synology when I debugged Ntfy with an incoming e-mail.

Thanks again and please let me know if there is anything else I can gather that might assist with this.

Mar 13 00:33:26 notification ntfy[4540]: DEBUG MAIL FROM: synology@mydomain.me (smtp_hostname=DiskStation, smtp_mail_from=synology@mydomain.me, smtp_remote_addr=192.168.1.28:53882, tag=smtp)
Mar 13 00:33:26 notification ntfy[4540]: DEBUG RCPT TO: synology@mydomain.me (smtp_hostname=DiskStation, smtp_rcpt_to=synology@mydomain.me, smtp_remote_addr=192.168.1.28:53882, tag=smtp)
Mar 13 00:33:26 notification ntfy[4540]: TRACE DATA (smtp_data=Date: Sun, 12 Mar 2023 20:33:26 -0400
Mar 13 00:33:26 notification ntfy[4540]: From: "=?UTF-8?B?Um9iYmll?=" <synology@mydomain.me>
Mar 13 00:33:26 notification ntfy[4540]: To: <synology@mydomain.me>
Mar 13 00:33:26 notification ntfy[4540]: Message-Id: <640e6f562895d.6c9584bcfa491ac9c546b480b32ffc1d@mydomain.me>
Mar 13 00:33:26 notification ntfy[4540]: MIME-Version: 1.0
Mar 13 00:33:26 notification ntfy[4540]: Subject: =?UTF-8?B?W1N5bm9sb2d5IE5BU10gVGVzdCBNZXNzYWdlIGZyb20gTGl0dHNfTkFT?=
Mar 13 00:33:26 notification ntfy[4540]: Content-Type: text/html; charset=utf-8
Mar 13 00:33:26 notification ntfy[4540]: Content-Transfer-Encoding: 8bit
Mar 13 00:33:26 notification ntfy[4540]: 
Mar 13 00:33:26 notification ntfy[4540]: Congratulations! You have successfully set up the email notification on Synology_NAS.<BR>For further system configurations, please visit http://192.168.1.28:5000/, http://172.16.60.5:5000/.<BR>(If you cannot connect to the server, please contact the administrator.)<BR><BR>From Synology_NAS<BR><BR><BR>
Mar 13 00:33:26 notification ntfy[4540]: , smtp_hostname=DiskStation, smtp_remote_addr=192.168.1.28:53882, tag=smtp)
Mar 13 00:33:26 notification ntfy[4540]: DEBUG Incoming mail error (error=unsupported content type, smtp_hostname=DiskStation, smtp_remote_addr=192.168.1.28:53882, tag=smtp)```
<!-- gh-comment-id:1506685943 --> @Robert-litts commented on GitHub (Apr 13, 2023): Hi! I just wanted to add to this with my use-case for HTML e-mails and Ntfy. I have been working to convert every conceivable device in my home to use Ntfy as my primary notification service. Unfortunately, several items still rely 100% on e-mail notification as their "only" form of notifications, so the SMTP aspect of Ntfy has been a lifesaver (thanks for all the troubleshooting we did over the past few months in Discord & in quickly tackling #610 !) The latest one I am trying to work on is my Synology NAS which has e-mail notifications, but use HTML formatted messages and therefore receive the "554 5.0.0 Error: transaction failed, blame it on the weather: unsupported content type" error. I know this was discussed/closed in #623 , but saw this issue/WIP PR #693 and wanted to add the code that I receive from Synology when I debugged Ntfy with an incoming e-mail. Thanks again and please let me know if there is anything else I can gather that might assist with this. ```Mar 13 00:33:26 notification ntfy[4540]: DEBUG Incoming mail (smtp_hostname=DiskStation, smtp_remote_addr=192.168.1.28:53882, tag=smtp) Mar 13 00:33:26 notification ntfy[4540]: DEBUG MAIL FROM: synology@mydomain.me (smtp_hostname=DiskStation, smtp_mail_from=synology@mydomain.me, smtp_remote_addr=192.168.1.28:53882, tag=smtp) Mar 13 00:33:26 notification ntfy[4540]: DEBUG RCPT TO: synology@mydomain.me (smtp_hostname=DiskStation, smtp_rcpt_to=synology@mydomain.me, smtp_remote_addr=192.168.1.28:53882, tag=smtp) Mar 13 00:33:26 notification ntfy[4540]: TRACE DATA (smtp_data=Date: Sun, 12 Mar 2023 20:33:26 -0400 Mar 13 00:33:26 notification ntfy[4540]: From: "=?UTF-8?B?Um9iYmll?=" <synology@mydomain.me> Mar 13 00:33:26 notification ntfy[4540]: To: <synology@mydomain.me> Mar 13 00:33:26 notification ntfy[4540]: Message-Id: <640e6f562895d.6c9584bcfa491ac9c546b480b32ffc1d@mydomain.me> Mar 13 00:33:26 notification ntfy[4540]: MIME-Version: 1.0 Mar 13 00:33:26 notification ntfy[4540]: Subject: =?UTF-8?B?W1N5bm9sb2d5IE5BU10gVGVzdCBNZXNzYWdlIGZyb20gTGl0dHNfTkFT?= Mar 13 00:33:26 notification ntfy[4540]: Content-Type: text/html; charset=utf-8 Mar 13 00:33:26 notification ntfy[4540]: Content-Transfer-Encoding: 8bit Mar 13 00:33:26 notification ntfy[4540]: Mar 13 00:33:26 notification ntfy[4540]: Congratulations! You have successfully set up the email notification on Synology_NAS.<BR>For further system configurations, please visit http://192.168.1.28:5000/, http://172.16.60.5:5000/.<BR>(If you cannot connect to the server, please contact the administrator.)<BR><BR>From Synology_NAS<BR><BR><BR> Mar 13 00:33:26 notification ntfy[4540]: , smtp_hostname=DiskStation, smtp_remote_addr=192.168.1.28:53882, tag=smtp) Mar 13 00:33:26 notification ntfy[4540]: DEBUG Incoming mail error (error=unsupported content type, smtp_hostname=DiskStation, smtp_remote_addr=192.168.1.28:53882, tag=smtp)```
BreizhHardware commented 2026-05-07 00:24:57 +02:00
Author
Owner
Copy link

@liamfleming26 commented on GitHub (Sep 5, 2023):

Just checking if there's any movement on this or any workarounds. I was ecstatic when I found out about this project which replaced a bunch of telegram bots serving a similar purpose for me.

I know nothing about Go so wouldn't know where to start. I did however use this project in the past to forward SMTP emails to the desired telegram channel. Unsure if it provides any pointers on the ContentType issues folks are facing.

(KostyaEsmukov/smtp_to_telegram)

<!-- gh-comment-id:1707235173 --> @liamfleming26 commented on GitHub (Sep 5, 2023): Just checking if there's any movement on this or any workarounds. I was ecstatic when I found out about this project which replaced a bunch of telegram bots serving a similar purpose for me. I know nothing about Go so wouldn't know where to start. I did however use this project in the past to forward SMTP emails to the desired telegram channel. Unsure if it provides any pointers on the ContentType issues folks are facing. ([KostyaEsmukov/smtp_to_telegram](https://github.com/KostyaEsmukov/smtp_to_telegram/blob/master/smtp_to_telegram.go))
BreizhHardware commented 2026-05-07 00:24:57 +02:00
Author
Owner
Copy link

@binwiederhier commented on GitHub (Nov 16, 2023):

I have decided to merge the original PR and add support for HTML-only emails. It comes up enough to merge in support, even though it is very sub-par. Don't expect too much. But at least mail will not be rejected anymore.

See https://github.com/binwiederhier/ntfy/pull/693

This will be in the next release.

<!-- gh-comment-id:1814610300 --> @binwiederhier commented on GitHub (Nov 16, 2023): I have decided to merge the original PR and add support for HTML-only emails. It comes up enough to merge in support, even though it is very sub-par. Don't expect too much. But at least mail will not be rejected anymore. See https://github.com/binwiederhier/ntfy/pull/693 This will be in the next release.
BreizhHardware commented 2026-05-07 00:24:57 +02:00
Author
Owner
Copy link

@binwiederhier commented on GitHub (Nov 16, 2023):

@Robert-litts I used your demo email in a test and it comes out nicely actually: github.com/binwiederhier/ntfy@859a4e4f79

<!-- gh-comment-id:1814624255 --> @binwiederhier commented on GitHub (Nov 16, 2023): @Robert-litts I used your demo email in a test and it comes out nicely actually: https://github.com/binwiederhier/ntfy/commit/859a4e4f79aafd258a24b90ebde56859242f6457
BreizhHardware commented 2026-05-07 00:24:58 +02:00
Author
Owner
Copy link

@Robert-litts commented on GitHub (Nov 17, 2023):

@binwiederhier Awesome & appreciate the effort on this one. I'm looking forward to testing this out. Thanks again.

<!-- gh-comment-id:1816830704 --> @Robert-litts commented on GitHub (Nov 17, 2023): @binwiederhier Awesome & appreciate the effort on this one. I'm looking forward to testing this out. Thanks again.
BreizhHardware commented 2026-05-07 00:24:58 +02:00
Author
Owner
Copy link

@teastrainer commented on GitHub (Nov 22, 2023):

This ist great news, and I can confirm, it works for me, too 🥳 Thank you so much!

<!-- gh-comment-id:1823637002 --> @teastrainer commented on GitHub (Nov 22, 2023): This ist great news, and I can confirm, it works for me, too 🥳 Thank you so much!
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
dependabot/npm_and_yarn/web/fast-uri-3.1.2
email-verification
attachment-no-http2
attachment-fixes
attachment-s3
config-generator
postgres-replica
dockers-v2
postgres-support
postgres-webpush+user+message
postgres-webpush+user
postgres-webpush
1364-copy-action
crashfix
user-header
scalar-api-docs
cancel-scheduled
update-available
windows-server
303-update-notifications
postgres
admin-ui
require-login
http-clipboard
message-cache-lock
debian-stripe
predefined-users
busy-timeout
template-dir
ipv6
client-ip-header
apns-fix
feat_optional_require_login
security-updates
pg-message-cache
templating-disallow
templating-3
templating-2
message-size-limit+delay-limit
remove-rate-topics
html-emails
cf-priority
acl-underscores
auth-user-header
markdown
img-attach
web-improvements
utf8-headers
matrix-507-reject
http-response-writer
new-homepage-design
e2e
canary
windows
electron
update-messages
webhook-templating
v2.22.0
v2.21.0
v2.20.1
v2.20.0
v2.19.2
v2.19.1
v2.19.0
v2.18.0
v2.17.0
v2.16.0
v2.15.0
v2.14.0
v2.13.0
v2.12.0
v2.11.0
v2.10.0
v2.9.0
v2.8.0
v2.7.0
v2.6.2
v2.6.1
v2.6.0
v2.5.0
v2.4.0
v2.3.1
v2.3.0
v2.2.0
v2.1.2
v2.1.1
v2.1.0
v2.0.1
v2.0.0
v1.31.0
v1.30.1
v1.29.1
v1.29.0
v1.28.0
v1.27.2
v1.27.1
v1.26.0
v1.25.2
v1.25.1
v1.25.0
v1.24.0
v1.23.0
v1.22.0
v1.21.2
v1.21.1
v1.21.0
v1.20.0
v1.19.0
v1.18.1
v1.18.0
v1.17.1
v1.17.0
v1.16.0
v1.15.0
v1.14.1
v1.14.0
v1.13.0
v1.12.1
v1.12.0
v1.11.1
v1.11.2
v1.11.0
v1.10.0
v1.9.0
v1.8.0
v1.7.0
v1.6.1
v1.6.0
v1.5.3
v1.5.2
v1.5.1
v1.5.0
v1.4.8
v1.4.7
v1.4.6
v1.4.5
v1.4.4
v1.4.3
v1.4.2
v1.4.1
v1.4.0
v1.3.2
v1.3.3
v1.3.1
v1.3.0
v1.2.5
v1.2.4
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.0
v0.0.5
v0.0.4
v0.0.3
v0.0.2
v0.0.1
Labels
Clear labels   
ai-generated

   
android-app

   
android-app

   
android-app

   
🪲 bug

   
build

   
build

   
dependencies

   
docs

   
enhancement

   
enhancement

   
🔥 HOT

   
in-progress 🏃

   
ios

   
prio:low

   
prio:low

   
pull-request
Mirrored from GitHub Pull Request

  
question

   
🔒 security

   
server

   
server

   
unified-push

   
web-app

   
website
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ntfy#508
No description provided.