Hey everybody, recently I was looking for a way to get notifications from various apps including proxmox etc. So the problem I ran into is that these apps sometimes only supported e-mail which I don’t like as I just don’t want to deal with it, and I also want my users to be able to reset there own passwords etc.

So I found a sort of hacky workaround which involves using mailrise(which is a SMTP gateway that redirects the e-mails to a diffrent platform), and then deliver it to an ntfy.sh topic which is then selfhosted, but still with push notifications due to the nifty work by the ntfy.sh creator. This let’s me get push notifications on my device while being nearly completley selfhosted, and I have started using this for my SSO(Zitadel), my Jellyseerr instance and a few other things.

And the cool thing is I can even have it work for multiple users, by saying “All e-mails going to example1@example.com go to the topic example1, while foo2@example.com goes to the topic foo2” and then by using the login system inside of ntfy.sh I can give each of my users a login that can acces there own topic and get notifications that way.

I have documented it on my blog which takes both the mailrise and ntfy.sh docker containers and gives the config files you need. It will by default let anybody write to a topic so you don’t need to authenticate mailrise, but you can change this to avoid spam. Incase there are any questions feel free to leave them in the comments, and sorry for the guide being shorter and less detailed than others as it was mostly ment for my internal docs but I thought it might be handy for others.

https://stetsed.xyz/posts/email-notifications-with-ntfy-and-mailrise/

  • StetsedOPB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Well… answer is I didn’t know NTFY had a built in SMTP server. I just used this combo cuz before I used it to send my notifications to discord which mailrise makes easy. I will say that mailrise does let you more granulary define what e-mails will be sent to what topic while NTFY just uses the recieving address as the topic which might not be wanted.(I can for example define stetsed@* which means it doesn’t matter if I use one of my other domains, or father@* which means he could use whatever domain he would want).