I have a private @gmail and a business @company.com (also via gmail), which I heavily rely on. Due to a recent data-leak somewhere, I’m now receiving unstoppable spam on my @gmail, and decided to set up a new account on proton and ditch @gmsil in favor of @example.com. I came across SimpleLogin, and thought that I could use that instead of protons custom domain feature for both @company.com and @example.com
Since I also host some stuff myself, I went through the self-hosting process of SimpleLogin, which was a pita dealing with postfix. But now, everything is running fine and I can send/receive @exampke.com emails, which I tested with @gmail and @company.com (gmail).
Even though it was a nice learning experience, I’m starting to wonder whether my setup is future proof and reliable, especially when it comes to spam. I really don’t want my @company.com mails to land in customers spam folders.
So my question is, how reliable is a self hosted email-forwarding solution, and how does it compare with a self-hosted mail service. Like, are these two equal in terms when it comes to precautions etc?
I would have a failsafe, like use a major email provider for emails that you need to go through for like work order government stuff.
Hosting your own email is a great learning experience and is fun to do; but your emails will get marked as spam, you’ll have to constantly perform maintenance, and have major reliability issues.
Most of the issues youll have are fine for personal use, but is dicey if you plan to migrate 100%
Edit: receiving email is less of an issue of sending. The forwarder should be reliable, however, its the sending from the forwarding address that would possibly be an issue.
Yea, I haven’t played with it too much. You’ll ever have to host your own SMTP server to send it or use gmail or protons SMTP service.
Doing it yourself might cause big companies to send your mail to spam or possibly just drop the packets cause you’re not using a trusted IP, have the wrong DNS settings, etc. and your ISP may even block port 25
This can be circumvented by using a SMTP relay service but can still have some issues like mail sending limits.
In my experience self hosting email it has pretty much been “set it and forget it”. I feel like there’s a lot of fud from people with misconfigured email servers (because there is a lot that can go wrong on setup). In every case I’ve seen where people are complaining about email deliverability I’ve found that they haven’t configured DKIM or rDNS properly. That doesn’t mean there can’t be issues, and I am sure it is technically possible to get sent to oblivion, but I feel like this issue might be somewhat overblown.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
I would have a failsafe, like use a major email provider for emails that you need to go through for like work order government stuff.
Hosting your own email is a great learning experience and is fun to do; but your emails will get marked as spam, you’ll have to constantly perform maintenance, and have major reliability issues.
Most of the issues youll have are fine for personal use, but is dicey if you plan to migrate 100%
Edit: receiving email is less of an issue of sending. The forwarder should be reliable, however, its the sending from the forwarding address that would possibly be an issue.
Yeah, I’m not that concerned about receiving, since I was able to send a mail with
swaksand it came through in proton.So, the forwarding system is basically like running an own mailserver, right?
Yea, I haven’t played with it too much. You’ll ever have to host your own SMTP server to send it or use gmail or protons SMTP service.
Doing it yourself might cause big companies to send your mail to spam or possibly just drop the packets cause you’re not using a trusted IP, have the wrong DNS settings, etc. and your ISP may even block port 25
This can be circumvented by using a SMTP relay service but can still have some issues like mail sending limits.
In my experience self hosting email it has pretty much been “set it and forget it”. I feel like there’s a lot of fud from people with misconfigured email servers (because there is a lot that can go wrong on setup). In every case I’ve seen where people are complaining about email deliverability I’ve found that they haven’t configured DKIM or rDNS properly. That doesn’t mean there can’t be issues, and I am sure it is technically possible to get sent to oblivion, but I feel like this issue might be somewhat overblown.