Re: Website link for 213.115.133.197

Hello.

Philip wrote:

> Hi. I just wanted to say the the IP removal system is all other than 
> perfect. Let me explain my problem. Our mailserver was an open relay for a 
> short time after a faulty upgrade.

According to DSBL database, this machine was running open proxy at port
20742 two weeks ago. In practice it means that this server was conrolled
by trojan software instead of legitimate owner; something much worse
than a simle open relay. Hope, this issue is fixed and the server is
completely reinstalled. Correct?

> This is now fixed. Now i want to remove 
> our server from your database since its now secure. However the confirmation 
> e-mail has to be sent to our ISP... 

As you wish. Other option is described at http://dsbl.org/faq-listed#notmine

> This is very very stupid for us running 
> our own mailserver. Now i have to call the postmaster at our ISP and ask him 
> to please click your confirmation link..

In my opinion, this way is very natural. The real abuse reports
regarding "static-213-115-133-197.sme.bredbandsbolaget.se" are
definitely sent to either <[email protected]> or
<[email protected]>; so, your ISP network security team may
 and should participate in this story.

> Even though it was OUR server not 
> THEIRS that was faulty.

If this server is really YOUR, and you want to be COMPLETELY responsible
for it's operations, you may wish to ask your ISP to publish your domain
 name in the reverse DNS. Now they publish their name; I believe, it
means that they want to be responsible.

> Hope they agree to click the link, if they say no we 
> will remain in your database and we will not be able to reach thousands and 
> thousands of e-mail adresses from our perfectly secure server.

To my knowledge, Mdaemon is known as insecure by default because of some
stable bugs in author's brains. It just trusts sender's domain in MAIL
FROM. Surely, there are known workarounds to make it secure; I hope, you
have implemented them already.

Best,
Alexey
DSBL volunteer

>  Well, that was all. Thanks.
>  Philip J.
>