Question
is anybody else having issues with delivering mail to charter.net?
- Posted on August 24, 2018
- EmailCentOS
Asked by David Nusbaum
I am suddenly having issues getting email delivered to charter.net and rr.com, which are both part of spectrum. I don’t know if the block is based on domain or ip or maybe a block of ips. I’m asking here on the off chance that a block on DO IPs got blocked for some reason.
SMTP via Posfix on CentOS
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Want to learn more? Join the DigitalOcean Community!
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
yep, that is the standard message charter is sending for too much mail from a range of addresses under the same ISP that they don’t like. Most of the other email providers at least put the word “range” into the message, but charter seems to be happy sending us on an endless chase to try to convince them that we are not sending too much mail.
There really is no way to get unblocked at Charter right now. I had one address that worked and 5 others that didn’t, but there is no way to know when more addresses might get added to the blocked range.
I believe the only way to have this fixed at DO is for DO to isolate a set of addresses for outbound email and then allow us to request them with an explanation of what email will be sent. But then DO would need a way to shutdown or punish offenders and that is more overhead on them.
So… sendgrid or aws sms or one of the other services out there. The situation is way beyond frustrating…
And the battle rages on… I consider having a private sending ip address essential to managing our sending reputation. We started with SendGrid, but the price went to $79 a month for any account that would support a private address. We moved to SparkPost, but now they are raising their prices from $29 a month (for my 50k messages and a private address) to $75 a month. We pay about $80 a month to host our application on DigitalOcean, so maying the same amount to simply send email seems ridiculous. I guess it’s time to try AWS. Would love to get some help here from DigitalOcean because putting customer in a position where they have to use an AWS service just doesn’t seem right. Couldn’t a block of addresses be set aside for outbound email and those addresses limited to longer term lease and some level of management so they are not abused and sent back to the pool?
It might be a general email deliverability problem - you can run a test with mailgenius.com and see if something is off with your technical setup and authentication.