*****SPAM***** about iperf

["Bob" <gqin --at-- cstnet.cn>]

Spam detection software, running on the system "rimantadine.ncsa.uiuc.edu", has
identified this incoming email as possible spam.  The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email.  If you have any questions, see
postmaster --at-- ncsa.uiuc.edu for details.

Content preview:  Hi, all, I am currently testing a link. I have 3 servers
  located in three points separately. The 3 servers are all running linux
  OS. The topology looks like this: [...] 

Content analysis details:   (7.1 points, 4.9 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 0.0 HTML_MESSAGE           BODY: HTML included in message
 0.2 HTML_FONT_FACE_BAD     BODY: HTML font face is not a word
 0.0 BAYES_50               BODY: Bayesian spam probability is 40 to 60%
                            [score: 0.4999]
 0.7 RCVD_IN_NJABL_PROXY    RBL: NJABL: sender is an open proxy
                            [159.226.58.79 listed in combined.njabl.org]
 2.2 RCVD_IN_SORBS_SOCKS    RBL: SORBS: sender is open SOCKS proxy server
                            [159.226.58.79 listed in dnsbl.sorbs.net]
 2.2 RCVD_IN_WHOIS_INVALID  RBL: CompleteWhois: sender on invalid IP block
          [159.226.251.23 listed in combined-HIB.dnsiplists.completewhois.com]
 1.8 AWL                    AWL: From: address is in the auto white-list

The original message was not completely plain text, and may be unsafe to
open with some email clients; in particular, it may contain a virus,
or confirm that your address can receive spam.  If you wish to view
it, it may be safer to save it to a file and open it with an editor.

--- Begin Message ---

• To: <iperf-users --at-- dast.nlanr.net>
• Subject: about iperf
• From: "Bob" <gqin --at-- cstnet.cn>
• Date: Tue, 15 Aug 2006 11:37:12 +0800
• Content-type: multipart/alternative; boundary="----=_NextPart_000_008C_01C6C05F.2655A150"
• Thread-index: AcbAHBfty6cOT7IgSaGdKyciHbokOQ==

Hi, all,

I am currently testing a link. I have 3 servers located in three points separately. The 3 servers are all running linux OS.

The topology looks like this:

 

Point1ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Point2ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ Point3

A^{-------------------------------------------------------}ï

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ÂÂÂÂ---------------------------------------------C

ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ÂÂB__â

I can traceroute between A-B, B-C, A-C successfully. And I can run iperf between A-B, A-C.

But when I ran iperf between B-C, no matter I configure B as server or client, iperf will halt after connection is built. I donât know what the reason is. It seems that network connections between the three points are ok. Could this problem be caused by security configuration?

Have you ever met such problem? Please give me some suggestions.

Thanks.

Bob

 

 

--- End Message ---