Protonmail relies solely on Firebase for receiving notifications on Android. While UniversalPush support is probably in the works, it may take some time until users on ROMs without GSF get built-in notifications.
The service requires a Linux box to run on, and can be deployed as a container or by running the provided binary. Building from source is of course also an option.
The service is a stripped down version of Hydroxide, the FOSS Protonmail Bridge alternative. There are no ports exposed, all communication is outwards. Communications to Proton servers use the Proton API. The service only receives events from Proton servers, and if the event is incoming mail, a notification is sent to a ntfy.sh server and topic of your choice. Other types of events are simply disregarded, and no other processing is done. The sent push event does not contain any detailed information.
EDIT: Starting from version v0.28.8-push7 the daemon supports HTTP basic auth for the push endpoint.
Disclaimer: I’m the author. All of the work is thanks to https://github.com/emersion/hydroxide, I’ve merely mutilized the great upstream project of most features for a single purpose. Issues, comments and pull requests are welcome!
Context is king. If there’s vital/time-dependent correspondence you’re waiting on, notifications can matter. But email in 2024 is pretty darn transactional, in which case a daily check is enough for most. Notifications for something suggest that I need to drop what I’m doing and attend to whatever arrived. That just doesn’t apply for service provider marketing, purchase receipts, etc.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Context is king. If there’s vital/time-dependent correspondence you’re waiting on, notifications can matter. But email in 2024 is pretty darn transactional, in which case a daily check is enough for most. Notifications for something suggest that I need to drop what I’m doing and attend to whatever arrived. That just doesn’t apply for service provider marketing, purchase receipts, etc.
And then the opsec angle comes into play: https://www.axios.com/2023/12/06/apple-google-requests-push-notification-data
Yeah I have to strongly disagree.
Which is why Proton’s notifications have been encrypted for years.