[GH-ISSUE #409] Add TLS encryption to SMTP receiver #315

New issue

Open

opened 2026-05-07 00:23:00 +02:00 by BreizhHardware · 1 comment

BreizhHardware commented

2026-05-07 00:23:00 +02:00

Owner

Originally created by @cmeis on GitHub (Sep 22, 2022).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/409

As of today the e-mail receiving server (for e-mail publishing) is only able to accept plain text connections.
I'd like to be able to use TLS encrypted (STARTTLS) connections, as notification contents might contain sensitive information.
As an option, I'd like to be able to make TLS mandatory on the server side, i.e. reject not encrypted connections via an config option in the server.yml.

Originally created by @cmeis on GitHub (Sep 22, 2022). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/409 As of today the e-mail receiving server (for e-mail publishing) is only able to accept plain text connections. I'd like to be able to use TLS encrypted (STARTTLS) connections, as notification contents might contain sensitive information. As an option, I'd like to be able to make TLS mandatory on the server side, i.e. reject not encrypted connections via an config option in the server.yml.

BreizhHardware added the

enhancement

server

labels

2026-05-07 00:23:00 +02:00

BreizhHardware commented

2026-05-07 00:23:00 +02:00

Author

Owner

@vnghia commented on GitHub (Nov 21, 2023):

Hi, any update on this. It seems that some services now requires a proper tls encryption to send the email so it is a block for me. I would like to work on this one if you think this FR makes sense

Edit: Currently I put a docker-mailserver to act as a relay server to ntfy

@vnghia commented on GitHub (Nov 21, 2023): Hi, any update on this. It seems that some services now requires a proper tls encryption to send the email so it is a block for me. I would like to work on this one if you think this FR makes sense Edit: Currently I put a `docker-mailserver` to act as a relay server to `ntfy`

BreizhHardware referenced this issue

2026-05-07 01:01:18 +02:00

[PR #315] [MERGED] docs: uptime kuma example #1268