Taking a quick google search, I think the problem is that they don't choke outbound port 25 through a central spam-checking service. So anyone can rent a host, start spewing spam, and not get shut off until the complaints are significant. If that's the case, I don't have much hope for this kind of service... it's likely to continue to have a "dirty" reputation.If you want to continue hosting there, get them to divert outbound 25 to an internal relay to throttle and discard spam. If they are unwilling to do that, change hosting, because that would make them spam-hosting friendly, triggering spam alerts from time to time.
as an isp, i can state that the big mail players are hopeless with the inbound spam filtering rules. at spire we are set up with comcast, yahoo, earthlink, usa.net, and some others with what is called a feedback loop. whenever those providers get email that is considered spam, we get sent a copy. and this is done for all the ips in our net (we don't require people to go through a single smtp server). there is the occasional infected system the spews out spam and we get that shut down quickly. but the normal day-to-day reports are for mailing lists the users are too lazy to unsubscribe from (and they all have standard boilerplate showing how to do that). so the end users just dump it into their spam folder and we get notified. theoretically by being on this feedback loop, we won't be blacklisted unless there is a huge amount of continuous unabated spam. but that doesn't always seem to be the case. still you may want to ask inmotion if they are on comcast's feedback loop system.
_______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
