Is there a self-hosted email client with push notifications?
-
but then you’d still have to have your mobile mail client go and download all this mail you said is a battery drain, so you’re sort of negating yourself.
That is precisely my point. I do not want a mobile or desktop client anymore. Just send a client which is running on a system which is always running anyway to send me a notification and I can then decide if I will check it out now or if it can wait.
Proprietary mobile clients often work similarly, they do the "heavy lifting" on the server side, send a notification, but only temporarily load the mails you explicitly view temporarily on the device. And thus, they use less battery and storage of the device. Another benefit for the unified client would be faster sync of mail status (e.g. read/unread) as it is only one client on the IMAP server instead of one on each device. And another benefit would be not having to migrate email clients when replacing devices.
-
Thank you, this definitely goes into the right direction and I will check them out!
-
Thanks for the suggestions, but no, I have not. I am not looking to replace my mail app, but to remove it from my device entirely.
-
Might be easiest to just find a mail host that supports push notifications and keep using the mail client that works for you. I host my own mailcow server and enable notifications for mailboxes I want to get notified for via Pushover.
-
So if you don't have any mail client, how do you receive the notification?
-
You can run a gui-less service that recieves and displays push notifications. I've programmed something like this before.
-
Well, no mail client. Browsers, ntfy, gotify and others can receive notifications too.
-
If I understand correctly, you want a PWA webmail that also supports the Push API?
-
Haven't tried it yet, but I am going to attempt https://mailcow.email/
-
I think mailcow only supports Pushover for notifications, but it may have changed.
-
99.9% of users don't have/use "server-side sieve filtering", so every new mail comes to the inbox only and the user might move it to a different folder later on. Because the workflow of most users is like this, you will have a hard time "going against the grain" if that makes sense.
My practical recommendation to you would be to just use a single inbox like everyone else if it's not critical for you to have "server-side sieve filtering".
I know it's hard sometimes to not have something work exactly like you wanted it. It happened to me many times also. Going with the majority is much easier and less time consuming than going the other painful, lone, hard route imo. Anyways, hope you find a good solution
