Re: Blacklisted - 210.187.111.86 and 204.3.218.98

Hello Joon.

On 17/04/06 08:06, Joon Kit wrote:

> Hi Dick Wesseling,
> 
> Thank you for a prompt reply. I'll try check with the lvin.org(our mail
> hosting company) and the recipient's mail server.

Unfortunately, the further investigation showed that the real source of 
problems is located at your server 210.187.111.86. Please look in 
"Messages from this host" section at 
http://dsbl.org/listing?204.3.218.98 : you run open mail relay at port 
258 and route all junk mail injected into this hole via 204.3.218.98.

And, unfortunately, your hosting company postmasters did not even try to 
investigate the incident before delisting request. As the result, 
204.3.218.98 have returned back in DSBL blasklist again nearly 
instantly: the hole is still open.

Please fix this severe vulnerability in your server 210.187.111.86 and 
ask your hoster to repeat the delisting procedure next Monday.

Alexey
DSBL volunteer


> Thank you.
> 
> Best Regards,
> 
> Joon Kit
> ----- Original Message ----- 
> From: "Dick Wesseling" <[email protected]>
> To: "Joon Kit" <[email protected]>
> Cc: <[email protected]>
> Sent: Monday, April 17, 2006 11:50 AM
> Subject: Re: IP Blacklisted -210.187.111.86
> 
> 
>> "Joon Kit" <[email protected]> wrote:
>>
>>> Our company IP is 210.187.111.86. However, when we check, it is not
>>> your database. We got this error when sending out mail
>>> (reason: 554 "This IP address has been blacklisted by DSBL-multihop-Host
>>> lookup-A record")
>> Your recipient's mail server is broken. A proper DSBL message always
>> contains the listed IP number.
>>
>> However, your message contains the following headers:
>>
>>> Received: (qmail 13119 invoked from network); 17 Apr 2006 03:37:52 -0000
>>> Received: from unknown (HELO lvin.org) (204.3.218.98)
>>>  by mail.ares.penguinhosting.net with SMTP; 17 Apr 2006 03:37:52 -0000
>>> Received: from redserver ([210.187.111.86])
>>>       by lvin.org (8.13.6/8.12.6) with SMTP id k3H3boFJ071378
>> And 204.3.218.98 is listed.
>>
>>> Could you please advise as I cant find any solution in your FAQ as well.
>> I suggest that you contact the postmaster of lvin.org (your ISP?).
>>
> 
> 
>