68

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
[-] irotsoma@piefed.blahaj.zone 2 points 1 day ago

Pop is download only (and optionally delete on server when downloaded), IMAP is sync so read states, moves, deletes, etc., will sync to the server and between all clients.

But both exist still, just most email providers want you to leave your email on their servers so they can charge you for storage, scan it for advertising, etc., and most people want the state to sync across devices, so a lot of places just don't implement it anymore and just allow either web-only or IMAP-only (usually paid since they don't get to show you ads).

And yes you can set up a local software to download email from another server offering POP or IMAP and then either use a client application or self hosted web application to view them. This is not too common so it might be harder to find instructions, but it's doable.

Which part are you concerned with. The biggest issue with email servers is trust. Many companies will refuse to connect to your SMTP server to send you emails or reject your emails your SMTP server is sending to them if you aren't on a whitelist or if your IP address has been used for spamming in the past and it's on a black list. The easiest way to get around this is to subscribe to an SMTP proxy service.

The other issue you may find will happen no matter if you selfhost or not. When using a custom domain, some servers have whitelists of domains in addition to IP addresses and if you aren't on it they will silently reject emails you send or that they were supposed to send to you. I have a couple of places (health care and financial companies mostly) who do this, so I have to use gmail, which ironically means the email is less secure, especially with Google's recent changes in policy about reading your emails.

this post was submitted on 02 Nov 2026
68 points (97.2% liked)

Selfhosted

63534 readers
458 users here now

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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS