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?

adonis
creator
link
fedilink
11Y

Yeah, I’m not that concerned about receiving, since I was able to send a mail with swaks and it came through in proton.

So, the forwarding system is basically like running an own mailserver, right?

@Boring@lemmy.ml
link
fedilink
English
21Y

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.

Create a post

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:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

  • 1 user online
  • 79 users / day
  • 112 users / week
  • 244 users / month
  • 852 users / 6 months
  • 1 subscriber
  • 1.53K Posts
  • 8.72K Comments
  • Modlog