Subject: Re: Anyone see what's wrong with this trace?
To: Bill Stouder-Studenmund <firstname.lastname@example.org>
From: Steven M. Bellovin <email@example.com>
Date: 09/04/2007 13:15:13
On Tue, 4 Sep 2007 10:06:18 -0700
Bill Stouder-Studenmund <firstname.lastname@example.org> wrote:
> On Mon, Sep 03, 2007 at 08:13:53PM -0400, Steven M. Bellovin wrote:
> > On Mon, 3 Sep 2007 16:28:51 -0700
> > Bill Stouder-Studenmund <wrstuden@NetBSD.org> wrote:
> > > On Mon, Sep 03, 2007 at 01:05:56PM +0100, Matthias Scheler wrote:
> > > > Do you use "fetchmail -d <...>"? If you do can you try
> > > > increasing the value?
> > >
> > > Yes and no. I've seen this with fetchmail -d 180 and with it at
> > > the command line.
> > >
> > > Any idea what's wrong? How would delaying more help? I'm starting
> > > to think I may know, but I'd like to hear your thoughts. :-)
> > >
> > With a large mailbox in mbox format, it can take a long time to
> > copy; you can also run into locking issues. Also, were you on a
> > slow link? I've had problems that way, too.
> I actually just switched to procmail into Maildir folders.
I was referring to the server side, not the client.
> However this is all happening rapidly. We send a SYN, we get a
> SYN-ACK, we reset the connection. Boom, boom, boom. The time stamps
> are 22:10:23.235746, 22:10:23.314508, and 22:10:23.314766.
> Why are we rejecting the Syn-Ack of the connection we're starting? Or
> why are we rejecting the connection?
--Steve Bellovin, http://www.cs.columbia.edu/~smb