Mail Server blacklisted

I’m getting some bouncebacks because email servers are rejecting the IP 204.14.110.252 and that IP has been blacklisted: Spam Database Lookup - 204.14.110.252

Can someone please take a look at this? Thank you!

We have already been working on this, their reasoning is due to a subnet that we do not even own. We have been trying to explain this to them.

Not sure if it’s related, but we’re listed in the SORBS DUHL list. My client can’t send to mail.com addresses as a result. I just submitted a ticket for help in getting us off that list.

Tim

Hi, any updates on this? It looks like the server is still on several lists (Spam Database Lookup - 204.14.110.252). Thanks!

We are working with upstream who has so many listed still :frowning:

APEWS has 0 contact methods. If you know one, please let me know. They seemed to be a clone of SPEWS that blacklisted almost everyone.
Rest are related to SORBS DUHL only. SORBS wants us to apply rDNS to this whole range that will take away reseller anonymity. The IP being talked about here is not even being used for outbound emails so no one is going to get affected easily.
Tim, may i get a copy of mail.com bounce please?

Tanmaya,

I’m afraid I no longer have the email from my client (trash and sent folders cleaned out). There’s a brief exerpt in ticket #MXZ-73100-900.

As for rDNS, I’d give up that bit of reseller anonymity to have mail that works well with those finicky providers like aol, mail.com, etc. But I’ll add that I’m using my reseller account a bit differently than some–I’m reselling to my web site development clients rather than just as hosting to all comers. So anonymity is a bit less of a concern to me than it is to some.

Tim

Tim, i already took care of your issue and replied there too. Are you/your client again seeing the issue?

No, my client isn’t having any further issues. I was replying to your note dated today at 6:19 am that said:

Perhaps forum message times got messed up or something.

Tim

ok. I thought it is some recent issue. I didn’t mean to ask for an already resolved issue.