From owner-freebsd-isp Sat Jul 15 0:39:27 2000 Delivered-To: freebsd-isp@freebsd.org Received: from strange.qualcomm.com (strange.qualcomm.com [129.46.2.27]) by hub.freebsd.org (Postfix) with ESMTP id 6138E37C4BE; Sat, 15 Jul 2000 00:39:22 -0700 (PDT) (envelope-from randy@qualcomm.com) Received: from [192.168.1.5] (vpnap-g1-012002.qualcomm.com [10.13.12.2]) by strange.qualcomm.com (8.9.3/8.9.3/1.0) with ESMTP id AAA27679; Sat, 15 Jul 2000 00:39:16 -0700 (PDT) Mime-Version: 1.0 Message-Id: In-Reply-To: <551931707624934073790@lists.pensive.org> References: <551931707624934073790@lists.pensive.org> X-Mailer: QUALCOMM Eudora v4.3 for Macintosh Date: Sat, 15 Jul 2000 00:31:49 -0700 To: "Lisa Casey" , From: Randall Gellens Subject: Re: Can't POP mail Cc: , Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 10:46 PM -0400 7/13/00, Lisa Casey wrote: > Hi, > > I'm sending this to a couple of FreeBSD lists plus the qpopper list in hopes > that I might get an answer in a hurry. > > I'm with an ISP. We are running a FreeBSD with Sendmail and qpopper box for > our mail server. We just changed upstream providers. > > We have a remote POP about 200 miles away and made the changeover to the new > upstream provider there today. > > Since the change, our users in the remote POP cannot connect to our mail > server. On their end they just get a "Can't connect to host" error message. > On my end, when I do a netstat on the freeBSD box I see users with IP > addresses corresponding to the remote location but they stay in SYN-RCVD. I > never see them as ESTABLISHED, and their mail never gets popped. Kind of sounds like maybe a firewall or other filter is blocking packets from the pop host to the users. > I did change /etc/mail/relay-domains to allow relaying from those IP > addresses (but that's a Sendmail problem, not a qpopper problem). These > users can't send mail through the system either. It doesn't seem like a Qpopper or sendmail problem; it's a networking issue. > What might cause soething like this? Any ideas are appreciated, I'll look > into anything -- I have customers that are not happy!! Maybe a TCP wrapper? Can you open POP, SMTP, or telnet sessions to the host? Can an affected user ping the host? -- Randall Gellens Opinions are personal; facts are suspect; I speak for myself only -------------- Randomly-selected tag: --------------- I have learned To spell hors d'oeuvres Which still grates on Some people's n'oeuvres. -- Warren Knox To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message