Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 6 Oct 1997 03:33:50 -0400 (EDT)
From:      Bradley Dunn <bradley@dunn.org>
To:        Peter Wemm <peter@netplex.com.au>
Cc:        hubs@freebsd.org, postmaster@ns3.harborcom.net, postmaster@mail.freebsd.sol.net
Subject:   Re: HEADS UP! mail black hole in freebsd relays somewhere?
Message-ID:  <Pine.BSF.3.96.971006030603.7844A-100000@ns2.harborcom.net>
In-Reply-To: <199710060632.OAA17272@spinner.netplex.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

ns3 does have anti-relaying provisions installed, but it allows relaying
for 204.216.27.0/24 which should pose no problems for the FreeBSD.org
machines.

ns3 is also behind a router that subscribes to Vixie's blackhole feed,
detailed at:
http://maps.vix.com/
That web page has a list of the addresses that are blocked by that feed.
Since all of those addresses are known spammers I don't think that should
be much of a problem.

ns3 is pretty lightly loaded at the moment, it doesn't do much other than
relay mail and act as an FTP server.

There are currently 1026 messages in its mail queue. I don't really know
where to look for problems. Do you have any headers that show a big lag
between the time the mail is received by ns3 and the time it is delivered?
Here are some headers I dug up:

**************
Received: from smyrno.sol.net (smyrno.sol.net [206.55.64.117])
        by ns2.harborcom.net (8.8.7/8.8.5) with ESMTP id CAA06710
        for <bradley@dunn.org>; Mon, 6 Oct 1997 02:56:24 -0400 (EDT)
Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by
smyrno.sol.net (8.8.5/8.6.12) with ESMTP 
id BAA22515; Mon, 6 Oct 1997 01:53:13 -0500 (CDT)
**************

The sol.net relay had a lag of a little over three minutes, and some of
that could be differences in the clocks.

**************
Received: from ns3.harborcom.net (ns3.harborcom.net [206.158.4.7])
        by ns2.harborcom.net (8.8.7/8.8.5) with ESMTP id CAA06556
        for <bradley@dunn.org>; Mon, 6 Oct 1997 02:55:05 -0400 (EDT)
Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18])
        by ns3.harborcom.net (8.8.7/8.8.5) with ESMTP id CAA16526;
        Mon, 6 Oct 1997 02:52:33 -0400 (EDT)
**************

ns3 had a lag of about three minutes as well.


As for lemis.com, here is a traceroute from ns3 to freebie.lemis.com (the
primary MX for lemis.com):
traceroute to freebie.lemis.com (192.109.197.137), 30 hops max, 40 byte
packets
 1  pve-rtr-3-E0 (206.158.4.1)  0.841 ms  0.663 ms  0.640 ms
 2  pve-rtr-1-E0 (206.158.4.62)  2.930 ms  2.662 ms  2.813 ms
 3  144.228.151.65 (144.228.151.65)  16.006 ms  13.433 ms  13.396 ms
 4  144.228.50.1 (144.228.50.1)  13.066 ms  13.231 ms  13.194 ms
 5  144.232.8.93 (144.232.8.93)  51.747 ms  52.107 ms  59.370 ms
 6  144.232.4.5 (144.232.4.5)  59.188 ms  51.272 ms  51.320 ms
 7  144.232.4.54 (144.232.4.54)  52.858 ms  52.368 ms  62.704 ms
 8  144.228.10.22 (144.228.10.22)  56.615 ms  56.010 ms  55.325 ms
 9  144.228.10.22 (144.228.10.22)  56.455 ms !H *  56.152 ms !H

It dies in Sprint. So it looks like there might be some routing problems
that need to be straightened out there. Apparently Sprint doesn't have a
route to 192.109.197.137. That is probably affecting more than just
FreeBSD mail.

Bradley Dunn
HarborCom




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.971006030603.7844A-100000>