mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 08:26:00 +02:00
[GH-ISSUE #1134] Topic password through email #801
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#801
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
Yesterday I setup the incoming email settings:
At the beginning it would not work and I would get a `Message not delivered response'
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.
@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.tldyou'd send tontfy-topic+tk_abc123...@domain.tld@Proximus888 commented on GitHub (Jun 18, 2024):
Thanks, awesome. I had not found that option in the documentation. Thanks again