4 ms·

This is largely a myth. I've run a pair of email servers - one small (maybe 250 outgoing emails/week) and one larger (80-100k/week) from 2007 to late 2016 and

by c2h5oh 9y ago

This is largely a myth. I've run a pair of email servers - one small (maybe 250 outgoing emails/week) and one larger (80-100k/week) from 2007 to late 2016 and had no problems with deliverability. It's just there are way more factors than SPF & DKIM: - static IPs that remain the same for years (no cloud) - IPs not in questionable subnets (no cloud) - forward-confirmed A DNS records for all sending servers - a valid SSL cert on MX servers (anecdotal evidence here) - never rapidly increase email volume. +50% day over day and +100% week over week is safe - rate limit outgoing email by recipients server/domain

djsumdog 9y ago
I think my biggest problems include limited e-mail output (<10 week really, because it's just me) and I'm currently on Linode; most likely on a spammy subnet. I do have static IPs for IPv4 and IPv6. Every spam analysis tool I've thrown at it says all my records are valid. My TLS cert is valid (paid for, but going to move to Lets Encrypt when it expires). I'm planning on moving to another hosting service like Vultr. They do require individuals apply to host e-mail servers (an unblock the SMTP port) so maybe I'll have better luck there.
- c2h5oh 9y ago
  Avoid cloud & cloud-like/mostly-vps providers. While they will most likely not have entire IP blocks straight blacklisted there might be a rule that just brings you closer to the spam score threshold. Oddly enough medium-large enterprise is more likely to include those rules - I've recently seen 20% bounce rate on a large mailing list spanning some 300 companies with most of the bounces being due to AWS IP blocks being blacklisted. That's why using Sparkpost for that kind of recipients is a bad idea (all their sending servers are on AWS). Going back to hosting - pick a company that: - lets you set PTR records for your IPs - lets you get your own IP block and assign it however you want (even it is just a tiny one) - offers primarily dedicated servers/collocation - even if their vps is going to be a bit more expensive

by c2h5oh 9y ago

djsumdog 9y ago

I think my biggest problems include limited e-mail output (<10 week really, because it's just me) and I'm currently on Linode; most likely on a spammy subnet. I do have static IPs for IPv4 and IPv6. Every spam analysis tool I've thrown at it says all my records are valid. My TLS cert is valid (paid for, but going to move to Lets Encrypt when it expires). I'm planning on moving to another hosting service like Vultr. They do require individuals apply to host e-mail servers (an unblock the SMTP port) so maybe I'll have better luck there.

c2h5oh 9y ago
Avoid cloud & cloud-like/mostly-vps providers. While they will most likely not have entire IP blocks straight blacklisted there might be a rule that just brings you closer to the spam score threshold. Oddly enough medium-large enterprise is more likely to include those rules - I've recently seen 20% bounce rate on a large mailing list spanning some 300 companies with most of the bounces being due to AWS IP blocks being blacklisted. That's why using Sparkpost for that kind of recipients is a bad idea (all their sending servers are on AWS). Going back to hosting - pick a company that: - lets you set PTR records for your IPs - lets you get your own IP block and assign it however you want (even it is just a tiny one) - offers primarily dedicated servers/collocation - even if their vps is going to be a bit more expensive