Problem with Jodo IPs being blacklisted

OK – I am getting extremely frustrated. Two of my clients are getting their mail returned from big ISPs as coming from blacklisted IP addresses. I keep getting assurances from Jodo that ‘everything is fixed now’ but am never told that they really understand the problem. I just put in another ticket – I imagine in a few hours they will reply – ‘problem fixed’ – and that will be it.
Based on pinging the IP getting bounced, 204.10.105.69, it appears to be SMTP7 – I thought the client was on MAIL5, but maybe not…

Does anyone else, other than Jodo, have any ideas on what is going on. The most recent response is posted below:

-----Original Message-----
From: MAILER-DAEMON@@ [mailto:MAILER-DAEMON@@]
Sent: Tuesday, October 17, 2006 8:58 AM
To: [email protected]
Subject: failure notice

Hi. This is the qmail-send program at @.
I’m afraid I wasn’t able to deliver your message to the following addresses.
This is a permanent error; I’ve given up. Sorry it didn’t work out.

[email protected]:
Connected to 204.127.198.26 but sender was rejected.
Remote host said: 550 204.10.105.69 blocked by ldap:ou=rblmx,dc=comcast,dc=net → BL004 Blocked for spam. Please see
Discovery Hub - News & Technology

— Enclosed are the original headers of the message.

You can check it on :
Free Tools - Software Reviews, Opinions, and Tips - DNSstuff

We are working with spamcop, to find out the reason of the listing. They have not communicated to us any spam sent from mail5.

We have two outgoing IPs on Mail5, both are listed with spamcop. We temporarily changed it to a 3rd.
We are working on this issue

So, what are my client’s options in the meantime? Can we switch mail servers? I don’t seem to have problems with most of my clients…

STILL HAPPENING AND MY TICKET NEVER SHOWED UP ON CEREBUS!!!

Hi. This is the qmail-send program at @.
I’m afraid I wasn’t able to deliver your message to the following addresses.
This is a permanent error; I’ve given up. Sorry it didn’t work out.

<[email protected]>:
64.62.140.120 does not like recipient.
Remote host said: 550-Message rejected - smtp7.mhere.biz (mail5.mhere.biz) 550-[204.10.105.69] is in an RBL, see Blocked - see 550 SpamCop.net - Blocking List ( bl.spamcop.net )
Giving up on 64.62.140.120.

— Enclosed are the original headers of the message.

How did you submit your ticket?

We are aware of the fact that Mail5 is still blacklisted. We have already disabled 2 spammers on Mail5. We should be unlisted shortly (in 2 hours)

Hosts, mail servers do get blacklisted from spamcop from time to time. We do everything to minimise it. But if you are on a shared mail server, this is the new reality of spammers and anti-spam groups like spamcop, etc

Please do not yell on this forum. We are doing our best here.

SpamCOP should delist one of mail5’s IPs in 20minutes.

OK, sorry for the yell. I am just getting frustrated.

I posted to Cerebus from:
http://resellerdesk.jodohost.com/support/index.php?x=&mod_id=5

I do understand the fact that on shared mail servers, it is hard to control what others do, and thus problems like this can creep up.

I think the biggest frustration that I have (and it seems from other postings that other people share this frustration), is that we, as resellers, are often not really told what went wrong, just that it was fixed. Without more specific information, I feel stupid talking to my client.

Not only do we host our clients, but our main business with them is actually development and technical support – I cannot afford to lose clients (especially the one in question here) as it would mean I would lose a big chunk of my income. Since I don’t want to lose my house and become homeless, I need to make sure my client remains happy.

Perhaps we could have back-up mail servers – I know that other clients, on Mail3 do not have issues. It probably wouldn’t work because of load balancing, but if there were a setting in hsphere to ‘switch’ smtp servers or something, then that could be a plus.

I am glad you mentioned that you caught two spammers. Prior to you mentioning that, I had no way to know if the problem really was going to be fixed. I know you have a 100mail item per day policy (especially if accounts have 100s of emails), but I am not sure how that is enforced…

Anyway, I am appreciative of the service I typically get, and I know you guys are trying to fix it, so, sorry, again, for the yell…
Tim

The issue was fixed 30min ago when spamcop unlisted main mail5 ip

which IP was released? 204.10.105.69 shows as still being listed by spamcop. Is that a secondary IP?
Thanks
Tim