DevHarm's avatar

IP exposure behind Cloudflare / Plesk setup

Hey all,

I’m running multiple websites (not just Laravel) on a VPS behind Cloudflare with deployment via Plesk.

Everything works great, except for one thing: email.

I feel like I’m basically forced to rely on services like Mailgun or Fastmail, mainly because:

  • My origin IP is still technically reachable
  • Self-hosting mail would expose that IP directly
  • VPS IP reputation for email is usually poor anyway

This becomes more noticeable when you run multiple apps/domains and don’t want everything tied to external providers.

So I’m curious:

  • Is anyone here actually self-hosting email for multiple sites/apps?
  • Or is using external providers just the standard these days?
  • Any setups where self-hosting is still viable without hurting deliverability or exposing your server?

Right now it feels like:

You can host your apps yourself, but email is basically outsourced by default. I was actually thinking about a different approach: Using a cheap shared hosting package purely for email.

Curious how others handle this.

Thanks!

0 likes
2 replies
jlrdw's avatar

Using a cheap shared hosting package purely for email.

You will probably have problems with quotas on a shared host but won't hurt to check with their sales.

martinbean's avatar

Using a cheap shared hosting package purely for email.

@devharm And you don’t think the IP addresses of shared servers are going to trash your deliverability rates…?

To be honest, I want absolutely nothing to do with email sending so yes, I will use a third-party service (specifically Amazon SES). They handle the infrastructure, the IP address reputation building, etc so I don’t have to worry about it.

Please or to participate in this conversation.