Checking re-issued IP addresses against Black-Lists
Checking re-issued IP addresses against Black-Lists.
I just received a new IP for a new ded server and one of my users ran into email issues because the IP was blacklisted 3 years ago by someone in Germany.
I cleared the blacklist, so it's all good now, and quite frankly, I should have checked it immediately. Although, given how LW really seems to strive for attention to detail, it struck as one of those things that should be in the dedicated server set up protocol to begin with.
This not a criticism of LW, whom quite frankly I believe have been flawless. It's just a thought a about something that enhances the ease of transition to a new server.
The RBL that caught your IP address as well as several others have been added to our auto-quarantine process.
Thank you for pointing this out, this is a positive change that we hope will
-
Admin[Deleted User] (Admin, Liquid Web) commented
Gary,
Thank you again for providing the blacklist. It is in the process of being added to our quarantine procedures, along with a few others that we believe will help prevent dirty IP addresses from being reassigned.
-
Gary Rockley commented
Yikes, just noticed I mis-typed the error code.
it was 553-Message Filtered, not 503.
-
Gary Rockley commented
Hi Alexandra,
Many thanks for the reply.
It does not surprise me that LW would already do that, and given how many blacklist sites there are, I'm sure one could fall through the cracks.
fyi, in case you need to add it your list, the blacklist in question was
http://dnsbl.inps.deI just noticed that's not an https url, which is surprising for a blacklist site.
The email was rejected on a 503-filter by symantec's messagelabs, so I guess they must reference that particular resource, since it was the only one I could find which had the IP flagged.
Either way, I am so incredibly impressed by Liquid Web's response and support that I considered this to be a minor issue. I just wanted to suggest it as something to consider, in case LW had not already implemented a protocol for this kind of thing.
Thanks again,
G.