Re: 62.166.230.74 and 62.166.230.75

Hi,
 
Well it was working fine this morning. We are a support company in
Belgium and we support Govt Departments. I run 2 mailservers here
because I'm the guy who gets all the crap work to do!. In spite of the
fact that [email protected] seems to be a different company, in fact
we are 2 hands on the same stomach, because my company, Networking
Technology, joined forces with Wauters IT when we left S.A. and came to
Belgium, so Frans is the MD and runs an Exchange Server on his end
(because he does MS support and as an MS HATER with a passion, I do
Novell and SuSE (Novell) Linux support. I'm also ex-Novell EMEA Support
for some years before I left them at the tender age of 65, to join up
with Frans.
 
I tried resending the mail just now and it went through without a
problem. In my book they should bring in the death penalty for spammers.
One of my customers is a Govt Dep and they get some +50,000 spam mails
per week (only 95 employees). If there is anything WE can do to assist
in killing spam, just ask. I monitor my mail servers 24 x 7 and even
with all the blacklists I have in place we still get anything up to 20
spam mails per day getting through.
 
I'm really sick of getting emails telling me to make my dick bigger or
to invest in some shady company or give my bank details to some black
twat from London who claims to be a Zulu and can't understand a single
word of the language! If we can help in anyway, let me know and if you
know of any spam filter I might not have, please also let me know. 
 
 
 
Henry Martin

>>> [email protected] 16-Dec-06 13:56 >>>
Hello.

I see the only explanation of the problem: a misconfiguration in
mail.wautersit.com machine. Neither any of of DSBL nameservers nor the
web-interface shows anything related to 62.166.230.74 and
62.166.230.75.
Note that even a host was listed in past and delisted, the
web-interface
still shows some history. We see nothing.

An indirect evidence is the "550" message content. A properly
configured
mailserver also provides the TXT record retrieved from DSBL in same
lookup, and this TXT points to the relevant DSBL web-page. Your
examples
are more laconic.

Compare:

In your examples:
550 5.7.1 62.166.230.75 has been blocked by multihop.dsbl.org

In my mailserver logs:
"555 5.7.1 Service unavailable; Client host [88.162.133.21] blocked
using list.dsbl.org; http://dsbl.org/listing?88.162.133.21" (
'http://dsbl.org/listing?88.162.133.21"' )

The only practical proposal is to contact the addressee via other
methods - fax or phone - and report the problem. It should be solved
by
the addressee's Postmaster.

16.12.2006 16:01, Henry Martin *****:

> I try not to think with things like this, I KNOW. That's why Ive
been
> working with computers since 1969.

My first programmer's certificate is dated 1977. So, I also remember
the
times When Computers Were Big :-)

Alexey


>  
> Return-path: <>
> Received: from corp.networkingtechnology.org
> (nw65-2.corp.networkingtechnology.org [62.166.230.75])
>  by corp.networkingtechnology.org with ESMTP; Sat, 16 Dec 2006
12:09:08
> +0100
> Received: from NTDOM-MTA by corp.networkingtechnology.org
>  with Novell_GroupWise; Sat, 16 Dec 2006 12:08:11 +0100
> Message-Id: <[email protected]>
> X-Mailer: Novell GroupWise Internet Agent 7.0.1 
> Date: Sat, 16 Dec 2006 12:08:11 +0100
> From: [email protected] 
> To: [email protected] 
> Subject: Message status - undeliverable
> Mime-Version: 1.0
> Content-Type: multipart/mixed; boundary="=__PartF6D23D8B.0__="
>  
> This is a MIME message. If you are reading this text, you may want to

> consider changing to a mail reader or gateway that understands how to

> properly handle MIME multipart messages.
>  
> --=__PartF6D23D8B.0__=
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
> Content-Disposition: inline
>  
> The message that you sent was undeliverable to the following:
>  
>  [email protected](550 5.7.1 62.166.230.75 has been blocked by
> multihop.dsbl.org)
>  
> Possibly truncated original message follows:
> 
>>>> [email protected] 16-Dec-06 13:00 >>>
> Hello.
> 
> 16.12.2006 14:40, Henry Martin *****:
> 
>> Hello!
>>
>> I run a GroupWise 7 Server, NO relaying of any kind and every
>> spamfilter I can lay my hands on in place. I also run a Border
>> manager 3.8 Firewall that not even a microbe can get through, but
in
>> spite of this your multihop.dsbl.org of stopping me from sending
>> important mails this morning for NO reason whatsoever. Your site
> says
>> that I'm not listed on either 62.166.230.74 or 62.166.230.75. We
are
>> NOT spammers. we are NOT an open relay and I object to being
blocked
>> by you
> 
> Can you please provide an exact example of a diagnostic message?
> Simply
> say, what makes you think that your mail delivery problems are
related
> to DSBL?
> 
> NB: a good practice is to censor left part of all real e-mail
> addresses
> in the evidences.
> 
> Alexey
> DSBL volunteer
> 
>> Henry Martin MCNE, CNI, CNS, MCSE.
>>
>>
>>
>>
>