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?
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?
Even if you are currently able to send mail without it being marked as spam, it doesn’t mean it will be the case forever. If your IP gets marked as a spam sender you’ll have trouble getting off that list
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.