Re: Website link for 216.174.29.130

Alexey Lobanov <[email protected]>
Newsgroups gmane.mail.spam.dsbl.admin
Message-ID <[email protected]>
Hi Keith.

On 23/09/2005 23:23, Keith Weller wrote:

> I am writting to try and figure out how to remove my IP from your list. Your
> company is the only blacklist company that currently has us listed and it is
> proving impossible to have ourselves removed. This is an executive suites
> (47 office) and no one sends out spam. The server did have an open relay and
> no PTR record (previously) which lead to our listing. This has been closed
> permanently and the PTR has been set up,

Not exactly so. Means, not "permanently". The history at 
http://dsbl.org/listing?216.174.29.130 shows that after successful delisting in July, 
this host was back in DSBL on August 09. And the reason was much worse than open 
relay: it was an open proxy at non-typical port number 3088. Was it a misconfigured 
legitimate program or a spammer's troyan?

> thus stopping spammers from sending
> through our server. I have tried to use the remove tool on your site to no
> avail. It constantly tells me no SMTP service. I then followed your link to
> the MX verify site to find out if the bug you spoke 

Looks like, your problem is not related to ECN. I can connect your host from my 
location with ECN enabled:

~$ cat /proc/sys/net/ipv4/tcp_ecn
1
~$ telnet esmail1.pbges.com 25
Trying 216.174.29.130...
Connected to esmail1.pbges.com.
220 esmail1.pbges.com (IMail 8.21 12265-1) NT-ESMTP Server X1

So, it seems to be some other connectivity glitch. Can any American member of this 
maillist test the connectivity? Awaiting for more external tests; I can say nothing 
definite now.

Alexey,
DSBL volunteer

> of was preventing me
> from recieving the email to [email protected]. I will attach the
> results below, it stated that all was working. Given this I tried again to
> remove us from your site and recieved the same SMTP error. Please let me
> know if there is anything else I can do. None of my tennants can send out
> their mail (unless using webmail services) and it is becoming very
> frustrating. The postmaster mail account is set up and should receive mail,
> all accounts can and do currently accept mail, they just can't send out do
> to this listing.
>  Results from the verify tool link fount in your contact section.
>   MX-VERIFY-CGI run for ``esmail1.pbges.com''
> 
> ------------------------------
> Doing resolver lookup for T=MX domain=``esmail1.pbges.com'' Questionable: NO
> MX DATA: domain=``esmail1.pbges.com'' We SIMULATE! Do have at least one MX
> entry added!
> 
> ------------------------------
> Testing MX server: esmail1.pbges.com <http://esmail1.pbges.com>
> 
> Address lookup did yield following ones:
> 
>   IPv4 216.174.29.130 <http://216.174.29.130>
> 
>  Testing server at address: IPv4 216.174.29.130 <http://216.174.29.130>
> 
> [ CONNECTED! ]
> 
>  220 esmail1.pbges.com <http://esmail1.pbges.com> (IMail 8.21 12225-1)
> NT-ESMTP Server X1
>  EHLO vger.kernel.org <http://vger.kernel.org>
>  250-esmail1.pbges.com <http://250-esmail1.pbges.com> says hello
>  250-SIZE 0
>  250-8BITMIME
>  250-DSN
>  250-ETRN
>  250-AUTH LOGIN CRAM-MD5
>  250-AUTH LOGIN
>  250-AUTH=LOGIN
>  250-EXPN
>  250 STARTTLS
> 
>  Excellent! It speaks ESMTP!
> 
>  MAIL FROM:<>
>  250 ok
> 
>  Fine, it accepts NULL return-path as is mandated by RFC 2821 section 6.1
> 
>  RSET
>  250 ok its reset
>  MAIL FROM:<[email protected]>
>  250 ok
>  RCPT TO:<[email protected]>
>  250 ok its for <[email protected]>
> 
> 
> Apparently OK!
> 
> Thank you for any help you can offer.
> 
> Keith (PBGES Manager)
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.