Does this app not do voicemail? I just got a voicemail and had to reset the standard google phone app as default to listen, then switch back to this one as default.
I imagine im missing something obvious here that i couls just search the web for, but i downloaded this app because of you all in the first place, so it is your collective responsibility to set it up for me as well.
As a user, if something like this was implemented in anything I use, as long as it’s opt-in (not opt-out), I would probably agree after I make sure I’m ok with the data I would be sharing.
Opt-out is always an instant “hell no” for me. It feels too much like a pusher.
I’d suggest trying FairEmail on your phone, email.faircode.eu, before trying to set up an email server.
I would ask if you have good knowledge of IMAP. That allows access to a unified inbox from several devices and you don’t have to own the server. It is far preferable to webmail for me.
I host my own email server and use many devices all over IMAP. If you need a server, nixos-mailserver is my recommendation. You could then try Roundcube on top but I bet you will use IMAP instead before you get there.
I am… Confused about your request. Why can’t you also have the same on your phone? Are you still using popmail? Sounds like simply setting your accounts to IMAP should solve your problem.
If you have a public IP and can forward ports, exposing SSH (with key-based login) is quite safe. You can browse the server storage and copy files to/from your phone.
If you can’t open ports you will need something that punches out of NAT and intermediates a connection to your phone. Simplest way is to use a service like Tailscale, you install and start it on both the server and your phone and they will see each other from wherever they are.
Nextcloud is simply software that runs on something. You might use DNS to find the something that your Nextcloud runs on … or not. A domain can cost as little as say £10/year (no details given - loose costing provided!) but you say you don’t want one.
You could do some weird stuff involving something like this: Your clients update a database on the server with their current IP address(es) and the server reciprocates in kind regularly.
For an internets conversation, both sides need to know IP address, protocol, and optionally port; for both ends. For example, a webby conversation might involve:
My end: 192.168.100.20/24, tcp port 2399 -> NAT -> 33.22.4.66, tcp port 2245 Remote web server: 99.22.33.44/37, tcp port 443
Now, provided both sides are warned off about changes to addresses and port numbers on a regular basis, then comms will still work.
Say, your home external IP address changes, then your browser writes that new address to the remote server and comms continue. Provided one end knows all the details of the other end at any point in time and can communicate local changes then we are good.
opensource
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.