From owner-freebsd-hubs Sun Oct 5 23:33:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA07842 for hubs-outgoing; Sun, 5 Oct 1997 23:33:21 -0700 (PDT) (envelope-from owner-freebsd-hubs) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA07824 for ; Sun, 5 Oct 1997 23:33:11 -0700 (PDT) (envelope-from peter@spinner.netplex.com.au) Received: from spinner.netplex.com.au (localhost.dialix.com.au [127.0.0.1]) by spinner.netplex.com.au (8.8.7/8.8.7/Spinner) with ESMTP id OAA17272; Mon, 6 Oct 1997 14:32:43 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199710060632.OAA17272@spinner.netplex.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: hubs@freebsd.org cc: postmaster@ns3.harborcom.net, postmaster@mail.freebsd.sol.net Subject: HEADS UP! mail black hole in freebsd relays somewhere? Date: Mon, 06 Oct 1997 14:32:22 +0800 From: Peter Wemm Sender: owner-freebsd-hubs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've heard a few comments about mail "disappearing" in the .com relays somewhere. Perhaps some anti-relaying is biting? Greg noticed that the ns3.harborcom.net had anti-relay stuff but that he was getting something like 90% of his mail via there, and only a small number via the .sol.net relay. Can we please check these two sites at least for mail jams? peter@hub[11:27pm]~-1009# host mail-relay.com.freebsd.org mail-relay.com.freebsd.org mail is handled (pri=20) by mail.freebsd.sol.net mail-relay.com.freebsd.org mail is handled (pri=20) by ns3.harborcom.net Greg's problem was solved when I directed his mail to go via mail.au.freebsd.org (he's in .au at the moment). This leaves nagging doubts about the .com relays. :-] He's had no mail coming in for periods of 8 hours or so at a time. Are these two relays overloaded? Do we need more .com relays? Cheers, -Peter -- Peter Wemm Netplex Consulting ------- Forwarded Message Date: Mon, 06 Oct 1997 15:28:37 +0930 From: Greg Lehey To: Peter Wemm Subject: Re: test to grog@lemis.com via AU relay from freefall On Mon, Oct 06, 1997 at 01:51:47PM +0800, Peter Wemm wrote: > Greg Lehey wrote: >> On Sun, Oct 05, 1997 at 10:02:36PM -0700, Peter Wemm wrote: >>> testing.. >>> -Peter >> >> Works fine. Thanks. And FreeBSD mail is coming in again. >> >> Did you work out what was wrong at the other sites? >> >> Greg > > Err, no, I don't know what's wrong yet.. I just added lemis.com to the .au > list in /etc/mailertable on hub.. Oh, well, thanks anyway. I wonder how many other people were affected. Greg ------- End of Forwarded Message From owner-freebsd-hubs Mon Oct 6 00:35:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA10800 for hubs-outgoing; Mon, 6 Oct 1997 00:35:53 -0700 (PDT) (envelope-from owner-freebsd-hubs) Received: from ns2.harborcom.net (root@ns2.harborcom.net [206.158.4.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA10795 for ; Mon, 6 Oct 1997 00:35:50 -0700 (PDT) (envelope-from bradley@dunn.org) Received: from localhost (bradley@localhost) by ns2.harborcom.net (8.8.7/8.8.5) with SMTP id DAA11439; Mon, 6 Oct 1997 03:33:50 -0400 (EDT) Date: Mon, 6 Oct 1997 03:33:50 -0400 (EDT) From: Bradley Dunn X-Sender: bradley@ns2.harborcom.net Reply-To: Bradley Dunn To: Peter Wemm cc: hubs@freebsd.org, postmaster@ns3.harborcom.net, postmaster@mail.freebsd.sol.net Subject: Re: HEADS UP! mail black hole in freebsd relays somewhere? In-Reply-To: <199710060632.OAA17272@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hubs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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 ; 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 ; 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 From owner-freebsd-hubs Mon Oct 6 15:03:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA02941 for hubs-outgoing; Mon, 6 Oct 1997 15:03:45 -0700 (PDT) (envelope-from owner-freebsd-hubs) Received: from smyrno.sol.net (smyrno.sol.net [206.55.64.117]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA02935 for ; Mon, 6 Oct 1997 15:03:39 -0700 (PDT) (envelope-from jgreco@solaria.sol.net) Received: from solaria.sol.net (solaria.sol.net [206.55.65.75]) by smyrno.sol.net (8.8.5/8.6.12) with SMTP id RAA08997; Mon, 6 Oct 1997 17:03:37 -0500 (CDT) Received: from localhost by solaria.sol.net (8.5/8.5) id RAA25901; Mon, 6 Oct 1997 17:03:34 -0500 From: Joe Greco Message-Id: <199710062203.RAA25901@solaria.sol.net> Subject: Re: Fwd: HEADS UP! mail black hole in freebsd relays somewhere? To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Mon, 6 Oct 97 17:03:31 CDT Cc: hubs@FreeBSD.ORG In-Reply-To: <19971006225131.33540@keltia.freenix.fr> from "Ollivier Robert" at Oct 6, 97 10:51:31 pm X-Mailer: ELM [version 2.4dev PL65] MIME-Version: 1.0 Content-Type: text Sender: owner-freebsd-hubs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I've heard a few comments about mail "disappearing" in the .com relays > somewhere. Perhaps some anti-relaying is biting? Greg noticed that the > ns3.harborcom.net had anti-relay stuff but that he was getting something > like 90% of his mail via there, and only a small number via the .sol.net > relay. Can we please check these two sites at least for mail jams? > > peter@hub[11:27pm]~-1009# host mail-relay.com.freebsd.org > mail-relay.com.freebsd.org mail is handled (pri=20) by mail.freebsd.sol.net > mail-relay.com.freebsd.org mail is handled (pri=20) by ns3.harborcom.net > > Greg's problem was solved when I directed his mail to go via > mail.au.freebsd.org (he's in .au at the moment). This leaves nagging > doubts about the .com relays. :-] He's had no mail coming in for periods > of 8 hours or so at a time. Are these two relays overloaded? Do we need > more .com relays? mail.freebsd.sol.net appears to be healthy. A quick telnet to the smtp port had no problems sending me a mail message. I don't see any unusual log messages, and no unusual kernel messages. There's a boatload of stuff in the queue (1170 req's) but the queue is running current stuff and the remaining stuff appears to be all "Operation timed out"'s and "Connection refused"'s. The number appears to be a bit higher than usual, but I've seen it worse before. There may be some delays in processing such a large queue. I'll throw mail3.sol.net into the alias too. If anyone notices any differences, please let me know. Administrivia: mail.freebsd.sol.net (a.k.a. mail2.sol.net) is due for replacement in the next month or so anyways, as part of routine upgrades and stuff. I'm not sure what to do about anti-relaying stuff: I'm in the difficult position of being a proxy for a lot of domains. Any advice? The machine must be able to accept mail from anywhere destined for one of the domains that sol.net services. The machine must be able to accept mail from one of those domains and send it to anywhere. I haven't seen a really good way to do this that doesn't require maintaining access lists. ... JG