<HTML>
<HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="OPENWEBMAIL" name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
<font size="2">>
> Now, the not so fun part - getting the server off the blacklists. And
<br />>
> the question.... Spend the whole day tracking down which blacklists its
<br />>
> on, and one at a time - submitting for removal? Or simply avoid that by
<br />>
> changing the IP address of the server itself?? A lot quicker that way,
<br />>
> but still a couple hours of work to get all the changes made in server,
<br />>
> DNS, routers, etc... Hummmm.....
<br />>
<br />>
Yeah, this is a good question. For checking which blacklists a server is
<br />>
on I often use this URL: <a href="https://mxtoolbox.com/blacklists.aspx" target="_blank">https://mxtoolbox.com/blacklists.aspx</a>
<br />>
<br />>
It allows you to run a check against 92 blacklists and the report then
<br />>
also has links to the respective lists so that you can chase them down.
<br />>
<br />>
Still: It's no fun.
<br />>
<br />>
--
<br />>
With best regards
<br />>
<br />>
Michael Stauber
<br />
<br />
<br />Yep - that's the same tool we use Michael. Thanks for sending that.
<br />
<br />Fortunately, I'm the server administrator - not the Customer Service Tech. So those guys get to deal with the customers, go through checking all the domains on that server for blacklisting, and follow the removal procedures. It will keep one or two of them busy the rest of the day, and that server only has about 25 domains on it.
<br />
<br />For the heavily loaded servers - I just change the IP address on the server itself. If they've correctly followed the IP addressing schema I laid out (yea, right!) - it only takes about 20 minutes to chance the IP on the server, update the DNS, and change the routing in the Cisco. But since we haven't always followed the IP addressing rules -- it can turn into a two or three hour job tracking down all the addresses and pointing them to the new server IP. What a PIA!
<br />
<br />But changing the Real World IP on the server itself clears up all the blacklist problems - as all e-mail is now coming from a different originating IP.
<br />
<br />
<br />BTW Michael. What's the possibility of a change ever coming to Sendmail, so that on a virtual hosting machine like this - the outgoing e-mail comes FROM the IP address assigned to that domain? That would prevent everybody else on a server being affected when one idiot lets a username/password out, or is hacked to send out SPAM. In that case - it would only affect his virtual site and e-mail coming out from him, instead of effectively blacklisting all domains on that server because the server's IP is blacklisted.
<br />
<br />Just wishful thinking??
<br />
<br />
<br />
<br />Chuck
<br />
<br />
<br />
</font>
</BODY>
</HTML>