On Wed, 25 May 2005 19:31:34 -0500 [EMAIL PROTECTED] wrote: > Midphase is NOT the one sending spam. Yes, they are the registrant > of the domain, and the server does resolve to a midphase server. > This is normal for a shared hosting company.
No, it's *not* normal in the slightest. Why on earth are they the registrant of the domain? They are making trouble for themselves (and their customers) if they are making themselves the Registrant of customer domains. (As you can see in this case). Technical contact, sure. Billing contact, quite possibly. Nameservers? Sure. Registrant? No. That's highly unusual and I'm not quite sure why you (or anyone else) are even accepting someone else being the owner of your domain. The Registrant is supposed to be the person who "owns" the domain and should be completely independent of both a) the person/company who actually performs the registration and b) whoever is providing hosting services or technical support at a given time. > I don't see how your point system really matters. Refusing mail from > my domain which is obviously NOT spam means there is something wrong > with your configuration Whilst not making comments about anyone's policies, it's worth pointing out that not everyone would agree, because not everyone in every circumstance applies the same rule that "any ham blocked is bad" or that "any ham blocked means my configuration is wrong". Some people have conscious policies of blocking mail from misconfigured hosts, hosts used for spamming or even hosts on ISPs that are spam- supporters, in the full knowledge that some ham will be/is caught. They may do this for a variety of reasons, including for example to apply pressure to customers of spammy ISPs to go elsewhere. That's their prerogative. So in fact some people would say that if their configuration is blocking the IP ranges managed by the Registrant of a non-forged domain used to spam, their configuration is working perfectly - regardless of whether it's possible some ham may originate from there. Looks to me like any problems here are mostly of your hosting company's making. I'm afraid if they do something crazy like setting themselves as the Registrant for thousands of customer domains, then guilt by association when spamming occurs is almost inevitable. Tim
