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?

  • Adrian Lee@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    6 hours ago

    I’ve taken the second approach you mentioned: I own the domain, host my email with a service provider (I use Zoho Mail), and manage my DNS through Cloudflare. Here are three insights I’ve gained from this experience.

    First, by managing your email provider and domain DNS separately, if you ever want to switch providers in the future, you’ll only need to update the MX and a few TXT records. Your email address will remain the same, and others won’t even notice.

    Second, set up SPF, DKIM, and DMARC right from the start. Be sure to enter the recipient address for DMARC aggregate reports so you can receive daily reports showing which servers are sending emails using your domain and whether they’ve passed verification.

    Third, even if a new domain passes all three checks, emails sent to Outlook may still end up in the spam folder at first. This is because the new domain lacks a reputation. It’s not a configuration error, and it takes time to gradually build that reputation.