Just to let you know. Comcast blacklisted us again today. The IP listed was 204.10.105.69. It has been removed by Comcast for now, but I wanted to let you guys know.
What was the error message from comcast, and has anyone checked the RDNS (reverse DNS) for all of the jodo mail servers lately?
Comcast often checks and blocks a server if the reverse DNS ptr is not exactly correct.
At a former h-sphere host, the very incompetent "admin"s would manage to screw it up (and/or blame psoft) about once a month, and DING comcast would block mail soon thereafter.
rDNS is there.. always has been 
Unfortunately I can’t take any more chances with Comcast blocking emails from this client so I have to find a new host for them and move them ASAP. Also, how can I trust putting any more clients on our reseller plan if I know they most likely can’t email Comcast addresses? Jodo has been the best host we have used this far, but honestly, this is a make or break issue for us.
I am getting alot of complaints with Comcast and unhappy clients. What is the statis on this???
any update??? I am losing a webhost customer because this happens so frequently!
hey guys – i agree this issue sucks.
I am moving a clients email server to google apps ( www.google.com/a/ ) but keeping web hosting with Jodo.
One side benefit is bandwidth and server space then get freed up on Jodo!
Sorry if this has been addressed, but i scanned through a couple threads and didnt see it DIRECTLY answered.
It seems that if Jodo set up a seperate SMTP server (maybe name it outmail.mhspherebiz.com), and set it up with SSL or some strict authentication, and it was intended only for use by actual clients sending mail out (and not passthrough, or forwarded mail) that could go a long way to addressing the blocking issues.
This is a slightly different approach than trying to move the forwards to another IP address (though same idea). But the advantage here would be that it could be implimented reseller-by reseller at their discression, maybe by adding outmail.resellerdomain.com to their dns, and then letting their clients use that as their SMTP server in their email program.
The only hangup I see is how this server would get the password info for authentication (assuming it would primarily reside on the current mail server assigned to the domain only). But that’s why you guys make the big bucks… if you have an answer for that, I think it would be a great presure release if we had a way to move clients to a “VIP” SMTP server that could be cleaner and less likely to be blocked… and without needing to leave Jodo altogether.
We are setting up a global clustered spam solution from DSPAM that will be installed infront of email traffic.
This is the most effective long term solution we have, and are moving towards it. We should have the software and servers up this weekend.
Have separate servers for customer SMTP is going to be a huge support challenge, with so many customers.. We are looking to implement the most transparent and painless solution possible.