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.

For those that already use ntfy.sh as a push provider for other apps, https://github.com/0ranki/hydroxide-push is a solution to get push notifications of new mail in Inbox.

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!

EDITED: Didn’t notice until looking at the image in this post the notification says “ProtoMail” instead of “Protonmail”. Changed the image and it’s fixed in the latest version, available when the GitHub action finishes

  • @mholiv
    2•5 months ago

    deleted by creator

    • @orankiOP
      2•5 months ago

      There is no way to log in or do anything externally after the daemon has started.

      The idea is just to provide push notifications, nothing else. The bridge creates a “login session”, because Hydroxide won’t poll for events if no users are logged in. In reality the SMTP or IMAP services are never started.

      If there’s an oversight somewhere, I’m more than happy to admit it and see to fixing it. I wouldn’t run this on a cloud VPS, just like I wouldn’t run Hydroxide either. Because all connections are outbound and the amount of data is small, a Raspberry Pi at home should be more than enough.

      I see you deleted the comment, going to leave this here anyway.

      • @mholiv
        3•5 months ago

        No problem. I deleted it because I realized that I did in fact misread things. :) You’re doing good here.

  • @orankiOP
    2•5 months ago

    Happy to report that version 0.2.28-push7, available today now supports HTTP Basic Authentication for the push topic!

    Password for basic auth is stored base64-encoded in $HOME/.config/hydroxide/notify.json, this is something that could be improved. Considering UnifiedPush always requires anonymous write access to the push topics, I don’t think this a very high-risk shortcoming.

    Suggestions for better password handling, as well as general feedback are welcome!