RE: 209.196.45.44

[ Note: I do not represent DSBL. I just track [email protected] to keep abreast
of possible issues that might affect my use of DSBL, and occasionally I help
out with questions. You may get responses from other subscribers to
[email protected], possibly even with dissenting opinions. ]

On Thu, 28 Dec 2006, Rick Paul wrote:

>  There are 2 ironies here.  It is difficult for the honest people such as
> myself to coexist with your service.  You know that you are personally
> dealing with an honest person, yet you are unwilling to help.

I'm helping as best I can. I cannot change DSBL policies, but I'm still 
using my copious spare time to inform you. Not that it seems to do a 
whole lot of good, but that's my problem, not yours.

>  I added a new IP which fixed the problem for most recipients.  For some
> reason, other recipients are resolving to my old IP.  (instead of
> webserver..com they are going to www..com)  This is why I need to be removed
> from the blacklist.

That problem description isn't sufficiently clear, and besides it
appears to be completely tangential to your DSBL listing.

>  When dealing with 2 third parties, it is very difficult to coordinate
> efforts.  Every time Godaddy makes a change, it takes me 1 week to test it
> out.  This makes things very difficult.  You must consider changing your
> policies to allow certain people who have been trying for months to have
> more than 1 try per week.  This policy of 1 try per week is only harmful and
> can have no benefit whatsoever.

I can not set DSBL policy, as I may have pointed out earlier, so please 
refrain from the insinuation that I could. Also, there is nothing to 
coordinate: the owner of a domain name is the only person to decide what 
happens to mail sent to his/her domain. Delegating that responsibility 
to a third party does not suddenly make another third party responsible 
for policy decicions regarding a domain. According to WHOIS, you 
delegated that responsibility to secureserverm.net.

>  You mention that godaddy can contact you, but DSBL can also contact 
> Godaddy.  It would be in the DSBL's best interest to resolve problems 
> with the large hosting companies.  I would assume that since you, an 
> admin, use the Godaddy service, that you would exercise due diligence 
> and try to resolve the problem.

I'm afraid you do not realize the magnitude of the spam problem. I send 
many thousands of notices each year to postmasters around the world 
regarding security issues that resulted in spam being sent to my users. 
All of these are properly researched. I get a couple of hundred 
automated replies, and one or two responses by a human (and the few 
humans that do respond get a dozen get-out-of-jail cards for the private 
block list at my work place). For all I know, all the other postmasters 
deleted all my e-mails to them unseen. Why should your problem be more 
important than the problems of my users?

Anyway, my earlier attempts at communicating with secureserver.net 
failed, so I did not move the domains I care about to their control, 
despite the fact that GoDaddy is dirt cheap. I have zero motivation to 
deal with them after having tried (and please consider spending your 
discretionary time on free service to the public before presuming any 
volunteer you talk to hasn't tried).

Your mileage may vary.