1993-05-29 - ADMIN: sequencing problems

Header Data

From: Eric Hughes <hughes@soda.berkeley.edu>
To: cypherpunks@toad.com
Message Hash: 0f508e4aa4896b190e2552a14be2f385e5adf2226aa9b6e5313de9a6ebf38635
Message ID: <9305281700.AA13903@soda.berkeley.edu>
Reply To: N/A
UTC Datetime: 1993-05-29 04:37:49 UTC
Raw Date: Fri, 28 May 93 21:37:49 PDT

Raw message

From: Eric Hughes <hughes@soda.berkeley.edu>
Date: Fri, 28 May 93 21:37:49 PDT
To: cypherpunks@toad.com
Subject: ADMIN: sequencing problems
Message-ID: <9305281700.AA13903@soda.berkeley.edu>
MIME-Version: 1.0
Content-Type: text/plain


Many have wondered why the mail comes out of order sometimes.  The
following comments are my surmise of the situation; I haven't done an
experimental confirmation of the situation.

The sequencing problem comes from the way that toad.com handles mail.
If it can't be delivered immediately upon arrival, it goes in the
queue.  If it can be sent out immediately, then it is sent out.  Now
toad.com routes to many sites through a relay at uunet; this relay
bogs down.  If toad.com can't connect to the relay, it queues the
mail.  The queue is processed only at intervals.  The next mail might
go out immediately, before the queue has been processed again.

I see the same thing at soda.  I'm not going to try to fix it.

Eric







Thread