Email Deliverability Issues
Cluster discusses challenges with email deliverability from self-hosted servers, including IP reputation, blacklists, spam filters, and best practices like SPF/DKIM/DMARC, often contrasting VPS providers with managed services.
Activity Over Time
Top Contributors
Keywords
Sample Comments
(I'm the author of TFA.)I have never had this issue. Generally the issue is either IP reputation of your server (common with VPS providers if you get a recycled IP of a previous spammer) or your domain name.Otherwise you are probably just unlucky enough to tickle the spam-prevention mechanisms in the almighty "algorithm" run by $BIGMAILER.I keep one "normie" email address at a $BIGMAILER for situations like this, but at this point in my life I mostly just shrug
It's more about inbound mail, many of the big mail services wont send TO you if you're on an ISP IP
It's not about configuration but rather your IP reputation and the struggle to not have your mail go straight to addressee's spam folder.
Wouldn't that imply that they have a lot of spammers on their network? As far as I understand, the value proposition is both "you don't need to worry about email" and "we have so many customers (sending legitimate emails that are very similar in content) and so little spam, we have great reputation and you're inheriting that reputation".If that doesn't work out, is their reputation not good enough? Is the receiving server too strict? Are those blocks oc
If you were doing everything right it would work, unless you sent email from an IP known to send spam in the past. That doesn't necessarily mean you did, but it does mean your IP did at some point. Given the saturation of the ipv4 space this isn't exceptionally unlikely. In any case, your post is contrarian and doesn't offer any substance aside from the fact that you are angry. That's kind of saddening because that was already pointed out as exactly the problem.
Same way Google broke SMTP. Even SPF isn't enough anymore.
They put me on a spam IP 2 months ago & i wasn't able to deliver to outlook, account got disabled later that day for 'abuse'. Same for Mailgun without the account being disabled, although they quickly switched me to a different IP and it was fixed. It has given me anxiety about deliverability, even with domain and everything configured correctly you could just be put on a bad IP, especially for low-priced options.
This isn't true at all. I self-host email, with full SPF/DKIM/dmarc, ESMTP, and my email isn't rejected anywhere. I'm sending and receiving via a Digital Ocean VPS. I've had the same IP for six years, and never had a problem.
Until Google and Microsoft decide they don't like your IP, or you missed a step in setting up the things you mentioned like SPF or DKIM. It is easy to stand up a mail server, but deliverability is still a challenge.
The trick to this is not hosting your mail server with a provider which has a bad reputation.Mine goes through a DigitalOcean droplet and my mail usually gets through (based on the assumption that if I received a reply, the other person must have received it!)By contrast a volunteer group I'm involved with was using OVH "because it's the cheapest". Suppliers and customers were routinely telling us the emails were going to spam. Moved to another provider (no idea who, th