Re: POP3 behavior on broken tcp connection

Steve Dorner <sdorner@uiuc.edu> Thu, 26 May 1994 19:35 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11233; 26 May 94 15:35 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa11229; 26 May 94 15:35 EDT
Received: from PO6.ANDREW.CMU.EDU by CNRI.Reston.VA.US id aa15265; 26 May 94 15:35 EDT
Received: (from postman@localhost) by po6.andrew.cmu.edu (8.6.7/8.6.6) id PAA20279; Thu, 26 May 1994 15:24:22 -0400
Received: via switchmail for ietf-pop3+@andrew.cmu.edu; Thu, 26 May 1994 15:24:21 -0400 (EDT)
Received: from po2.andrew.cmu.edu via qmail ID </afs/andrew.cmu.edu/service/mailqs/q004/QF.0htDQAS00UdaFFK05t>; Thu, 26 May 1994 15:23:00 -0400 (EDT)
Received: from ux1.cso.uiuc.edu (ux1.cso.uiuc.edu [128.174.5.59]) by po2.andrew.cmu.edu (8.6.7/8.6.6) with SMTP id PAA20817 for <ietf-pop3+@andrew.cmu.edu>; Thu, 26 May 1994 15:22:42 -0400
Received: from dorner.slip.uiuc.edu by ux1.cso.uiuc.edu with SMTP id AA11064 (5.67b8/IDA-1.5 for <ietf-pop3+@andrew.cmu.edu>); Thu, 26 May 1994 14:22:18 -0500
Received: from [192.17.5.3] by dorner.slip.uiuc.edu with SMTP id AA27500 (5.67b/IDA-1.5 for <ietf-pop3+@andrew.cmu.edu>); Thu, 26 May 1994 14:22:29 -0500
X-Sender: sdorner@192.17.5.1
Message-Id: <aa0aa12f0c021015b711@[192.17.5.3]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 26 May 1994 14:22:11 -0500
To: POP3 IETF Mailing List <ietf-pop3+@andrew.cmu.edu>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Steve Dorner <sdorner@uiuc.edu>
Subject: Re: POP3 behavior on broken tcp connection

At 12:21 PM 5/26/94, John Gardiner Myers wrote:
>I was under the impression that current versions of Eudora didn't keep
>the connection open long enough to matter.  Could you clarify?

Sure.  Traveller is in Beijing, on horrendously expensive but poor quality
phone lines.  Dials into server, where he finds 50 new messages.  Eudora
begins to suck them over, DELE'ing each one after it arrives.  After 20
messages, phone goes dead.  Popper does not enter the update state, and so
neither does it do the deletions nor does it update the Status: headers.
Traveller dials again, and Eudora is presented with exactly the same
maildrop as last time.  Starts downloading all the messages again, loses
the connection after 20 messages.  Repeat until credit card limit is
reached, without fetching all mail.  :-(

If the DELE's don't happen and the LAST value isn't updated, there's no way
out of this.  Except a whole different architecture, which is what I'm
working on doing for new versions.

>Do current versions of Eudora ensure messages are written out to disk
>and will survive a crash before they send out DELE commands?

Yes.  Write it to disk, flush disk cache, read it back, DELE.

--
Steve Dorner, Qualcomm Incorporated
 "There's nothing wrong with you that can't be cured
  with a little Prozac and a polo mallet." - Woody Allen