QUOTE(Telarin @ Sep 1 2006, 08:10 AM)

The IP in question is 209.239.36.24. Hopefully I can give him enough information to go gripe to his host about their incompetence and get the thing fixed.
Looks like the owner of the IP is alabanza.com and they aren't interested in reports on it...
I have a lot of past experience with Alabanza, first as a dedicated server customer, and then as a shared hosting customer of one of thier many hosts, and I don't think you're going to have much luck. While we were on Alabanza shared hosting, we were constantly getting blocked by AOL and others.
Your customer seems to be getting their hosting from "1host.com" which is in turn hosted by Alabanza. The problem is, on their dedicated servers, all of the outgoing email is sent using the single IP assigned to that particular server, so if any one of the hundreds of other clients on that box sends something bad out, mail from all the other clients is affected, in terms of blacklists, etc. Furthermore, their error bounces are done "after the fact" rather than during the incoming SMTP sessions, so those servers are prone to being listed due to UUBE.
Your customer won't be allowed to communicate with Alabanza at all, in that they are a "customer of a customer" so they'll have to report this to their direct upstream hosting company and hope for the best. My recommendation would be for them to find a host that enables them to use their assigned IP address (for their domain) to be used when sending emails, so that they don't get "tarred" by all the others sharing a common node IP.
DT