I'm tempted to move to email with my own domain, but don't really care about the server side of things, I guess I'm following the line that self hosted email is not easy to do, and not sure how reliable I can make my servers.

The other option is to have some other system do the email hosting, and if it is through my domain then there should be no issues with moving around if needed. Hosting all the email archive isn't really needed either, I'd be fine self hosting or storing the archive.

Is there a set up where some remote service handles email exchange, and you just sync with it eg through POP style interfaces? Id actually prefer if my own server was doing the sync rather than a desktop running Thunderbird etc, that way it is kind of self hosted but also robust to down time. What's the best practice along these lines?

you are viewing a single comment's thread
view the rest of the comments
[–] [B] 3 points 1 week ago* (last edited 1 week ago)

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters More Letters
CGNAT Carrier-Grade NAT
DNS Domain Name Service/System
IMAP Internet Message Access Protocol for email
ISP Internet Service Provider
NAT Network Address Translation
POP3 Post Office Protocol v3, for email; contrast IMAP
SMTP Simple Mail Transfer Protocol
VPS Virtual Private Server (opposed to shared hosting)

[Thread #156 for this comm, first seen 2nd Nov 2026, 23:10] [FAQ] [Full list] [Contact] [Source code]

  • source