[GH-ISSUE #1134] Topic password through email #801

Closed
opened 2026-05-07 00:27:40 +02:00 by BreizhHardware · 2 comments

Originally created by @Proximus888 on GitHub (Jun 18, 2024).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1134

Question

I selfhost my own NTFY server. To not let everyone use my server I have the following settings in server.yml, so only authenticated users can post on topics.

 auth-file: "/etc/ntfy/user.db"
 auth-default-access: "deny-all"

Yesterday I setup the incoming email settings:

smtp-server-listen: ":25"
smtp-server-domain: "domain.tld"
smtp-server-addr-prefix: "ntfy-"

At the beginning it would not work and I would get a `Message not delivered response'

The response from the remote server was:

554 5.0.0 Error: transaction failed, blame it on the weather: error: {"code":40301,"http":403,"error":"forbidden","link":"https://ntfy.sh/docs/publish/#authentication"} 

Till I made the topic accessible to everyone then it worked perfectly. Now my question is if there is a way to post incoming email to a user locked topic? A way to pass on credentials or a setting I missed.

Thanks for the awesome work, NTFY has fully replaced pushover for me and use it for all my services.

Originally created by @Proximus888 on GitHub (Jun 18, 2024). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1134 :question: **Question** <!-- Go ahead and ask your question here :) --> I selfhost my own NTFY server. To not let everyone use my server I have the following settings in server.yml, so only authenticated users can post on topics. ``` auth-file: "/etc/ntfy/user.db" auth-default-access: "deny-all" ``` Yesterday I setup the incoming email settings: ``` smtp-server-listen: ":25" smtp-server-domain: "domain.tld" smtp-server-addr-prefix: "ntfy-" ``` At the beginning it would not work and I would get a `Message not delivered response' ``` The response from the remote server was: 554 5.0.0 Error: transaction failed, blame it on the weather: error: {"code":40301,"http":403,"error":"forbidden","link":"https://ntfy.sh/docs/publish/#authentication"} ``` Till I made the topic accessible to everyone then it worked perfectly. Now my question is if there is a way to post incoming email to a user locked topic? A way to pass on credentials or a setting I missed. Thanks for the awesome work, NTFY has fully replaced pushover for me and use it for all my services.
BreizhHardware 2026-05-07 00:27:40 +02:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@wunter8 commented on GitHub (Jun 18, 2024):

As seen in the last code example of this section of the docs, you can include an access token in the "to" email address.

So instead of sending to ntfy-topic@domain.tld you'd send to ntfy-topic+tk_abc123...@domain.tld

<!-- gh-comment-id:2175968062 --> @wunter8 commented on GitHub (Jun 18, 2024): As seen in the last code example of [this section](https://docs.ntfy.sh/publish/?h=token#e-mail-publishing) of the docs, you can include an access token in the "to" email address. So instead of sending to `ntfy-topic@domain.tld` you'd send to `ntfy-topic+tk_abc123...@domain.tld`
Author
Owner

@Proximus888 commented on GitHub (Jun 18, 2024):

As seen in the last code example of this section of the docs, you can include an access token in the "to" email address.

So instead of sending to ntfy-topic@domain.tld you'd send to ntfy-topic+tk_abc123...@domain.tld

Thanks, awesome. I had not found that option in the documentation. Thanks again

<!-- gh-comment-id:2175978449 --> @Proximus888 commented on GitHub (Jun 18, 2024): > As seen in the last code example of [this section](https://docs.ntfy.sh/publish/?h=token#e-mail-publishing) of the docs, you can include an access token in the "to" email address. > > So instead of sending to `ntfy-topic@domain.tld` you'd send to `ntfy-topic+tk_abc123...@domain.tld` Thanks, awesome. I had not found that option in the documentation. Thanks again
Sign in to join this conversation.
No milestone
No project
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#801
No description provided.