From owner-freebsd-isp  Mon Jan  6 08:34:31 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id IAA14968
          for isp-outgoing; Mon, 6 Jan 1997 08:34:31 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id IAA14963
          for <freebsd-isp@freebsd.org>; Mon, 6 Jan 1997 08:34:28 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA21269; Mon, 6 Jan 1997 09:34:12 -0700 (MST)
Date: Mon, 6 Jan 1997 09:34:12 -0700 (MST)
Message-Id: <199701061634.JAA21269@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: Peter Hawkins <peter@clari.net.au>
Cc: freebsd-isp@freebsd.org
Subject: Re: mail weirdness
In-Reply-To: <199701061057.VAA11651@rhiannon.clari.net.au>
References: <199701061057.VAA11651@rhiannon.clari.net.au>
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Has anyone any clues what may be going on here?
> 
> I have a customer who needs to mail large uuencoded zip files daily.
> He also downloads largish (>100k) files regularly via his browser.
> 
> The browser is able to download the files without problem so his
> link can take such transfers without problems when he is using the
> FTP protocol.
> 
> When he tries to download (smtp) or upload (pop) mail, the transfer
> is frequently (though not always) interrupted and although he remains
> connected, no more packets are sent.

FWIW, there are some folks running BSDi who see the same problem.  I'm
beginning to smell some sort of incompatability in the BSD stack and
Qualcomm's popper, but I personally have users who download megabytes of
email every day w/out a problem, so maybe it's a modem setup problem?

I'm assuming you're using a modem, correct?



Nate