I know the adage that self-hosting email is hard. I use a third party smtp server to send emails for my Lemmy instance in order to guarantee delivery, for example.

However, other than potential uptime, what are the disadvantages to setting up self-hosted incoming email?

Incoming email is like 99% of my email usage. I’m happy to use a third party mail provider for outgoing email, but don’t see why I shouldn’t simply host incoming email myself.

Thank you <3

  • TheOneCurly@lemmy.theonecurly.page
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Most people complain about spam. I think you’ll be surprised just how much incoming spam you get and how hard it is to sort though it. Not to say it’s not worth doing, but that’ll be the hard part.

    • james@lemmy.jamesj999.co.uk
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Agreed. Sensible to only do the incoming too, I had an outgoing one and it got hijacked because SMTP security seems to default to ‘least secure’. For example if there is a single character out of place in the config file, I found it basically opened everything up rather than reporting an issue :)

  • Moonrise2473@feddit.it
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    The main drawback is having your ip address bound to your domain, which with a whois can equal to your name and address

    Maybe i’m just paranoid, spoiled by cloudflare protection

  • EskueroA
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    It’s probably worth it for registration accounts you want not to give your real email for but still won’t be a single one time usage like ten minute mail services.

    You create a single alias and when you are done with it simply drop the alias and never hear about it again.

  • LyingPenguin@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    I don’t see anything wrong with self-hosting the receiving part. Especially with something like mailcow it shouldn’t be any more difficult than hosting anything else, provided you have backups in place and will be able to get the server up and running again within 24 hours to not lose any emails. Yes, spam may be an issue, but mailcow has useful defaults configured and it works okay-ish for me.

    Btw, they also allow for configuring outbound relays quite easily. This allows for simpler configuration on the client-side. I have it set up so that all emails sent through mailcow will be forwarded to mailgun, for example.

  • binwiederhier@discuss.ntfy.sh
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    I hosted my incoming mail for years with a minimal postfix config that would just relay to Gmail. That got me individual email addresses per service (e.g. grubhub@mydomain.com, …) that I could turn off when a service got annoying.

    It worked wonderfully without issues for years. And by years i mean 8-10 years!

    Recently, 11 months ago, i noticed that some mails were not relayed anymore, and i ultimately switched to Cloudflare for that feature. You can read more about that here: https://www.reddit.com/r/selfhosted/comments/vqk4j9/mail_relay_as_a_service_moving_away_from/

    That said, if you only want to store the incoming mail, I don’t think you’ll have issues beyond spam, a lot of spam.

    Good luck.