Right, so it looks like AOL hates DreamHost.
Perhaps not the entire company, just their customers. I really wish they’d start seeing things from the point of view of the people who give them money on a regular basis - their own customers. I have personally sent numerous emails to the AOL postmaster (from my AOL accounts), asking them to fix their damn mail blocks.
I have always hated AOL’s server-side mail shankers. Back when email over at vandusens.us still worked (yet another problem I’ve been trying to get fixed; long story there), I made several attempts to have my domain whitelisted on the AOL server, just so I could send email to my own accounts over there. They never would do it, because the server was shared between 1000 domains. Well, ever since I moved to Dreamhost (the 23rd largest web host in existance), it’s been rather spotty. I can send mails one day, but not the next. And of course, if any of my members (forums; blog; etc.) register with an AOL address, they will bounce on a regular basis, generating several problems for me.
The problem is, Dreamhost’s mail servers are fixed up on AOL’s servers to be able to send mail there - but if their servers trigger a volume alert (which they do on a daily basis, being one of the larger hosting companies), ALL domains are instantly blacklisted by their robots, and a human has to come reset them. Of course, several spammers DO reside on Dreamhost, and they are dealt with in a most brutal fashion. That still doesn’t stop most large domains from blacklisting their servers; therefore, they are creating an environment where if one is on a large email service (i.e. AOL, hotmail, gmail, yahoo), then all mail is sent but not all mail is recieved. However, if if you have a smaller service (i.e. mattfast1.com), you recieve all mail but cannot send to some trigger-happy servers.
There needs to be a better solution than having blacklists consisting of IP addresses. Perhaps we can start actually targeting spammers AND the companies that hire them to make them stop - permanently.
0 Response to “A complete shank”