---------------------------------------------------------------------

              ***************************************
              **       This is a warning only      **
              **    No action is required by you   **
              ***************************************

Re: Message to felix@mail.sisna.com

Your message  has not  been  delivered  after  1 hours.   Attempts to
deliver your message will continue for a further  2 hours.  If it has
still not been delivered,  it will be returned to you.  The first few
lines of your message are repeated below.

---------------------------------------------------------------------
Your message follows:

>Received: from [205.138.107.34] by mail.sisna.com (NTMail 3.01.03) id ga939828; Tue, 9 Jul 1996 21:09:31 -0600
>Received: from [205.138.107.34] by mail.sisna.com (NTMail 3.01.03) id fa939307; Tue, 9 Jul 1996 21:02:34 -0600
>Received: from [205.138.107.34] by mail.sisna.com (NTMail 3.01.03) id ha938269; Tue, 9 Jul 1996 20:52:31 -0600
>Received: from [205.138.107.34] by mail.sisna.com (NTMail 3.01.03) id ba938055; Tue, 9 Jul 1996 20:49:43 -0600
>Received: from [205.138.107.34] by mail.sisna.com (NTMail 3.01.03) id ha937125; Tue, 9 Jul 1996 20:41:32 -0600
>Received: from [205.138.107.34] by mail.sisna.com (NTMail 3.01.03) id pa936509; Tue, 9 Jul 1996 20:35:31 -0600
>Received: from [205.138.107.34] by mail.sisna.com (NTMail 3.01.03) id ja934917; Tue, 9 Jul 1996 20:16:51 -0600
>Received: from [205.138.107.34] by mail.sisna.com (NTMail 3.01.03) id ya933736; Tue, 9 Jul 1996 20:03:23 -0600
>Received: from [205.138.107.34] by mail.sisna.com (NTMail 3.01.03) id wa933032; Tue, 9 Jul 1996 19:53:38 -0600
>Received: from [205.138.107.34] by mail.sisna.com (NTMail 3.01.03) id ia931380; Tue, 9 Jul 1996 19:32:00 -0600
>Received: from [205.138.107.34] by mail.sisna.com (NTMail 3.01.03) id na929903; Tue, 9 Jul 1996 19:10:11 -0600
>Received: from [128.101.131.50] by mail.sisna.com (NTMail 3.01.03) id fa926775; Tue, 9 Jul 1996 18:36:27 -0600
>Return-Path: <vanagon@lenti.med.umn.edu>
>Received: from halfdan.med.umn.edu by mhub0.tc.umn.edu; Tue, 9 Jul 96 19:27:06 -0500
>Date: Tue, 9 Jul 1996 19:26:30 -0500
>Received: from  (localhost) by halfdan; Tue, 9 Jul 1996 19:26:30 -0500
>Message-Id: ya917746.mbx
>Errors-To: gsker@lenti.med.umn.edu
>Reply-To: root@sisna.com
>Originator: vanagon@lenti.med.umn.edu
>Sender: vanagon@lenti.med.umn.edu
>Precedence: none
>From: NTMail <root@sisna.com>
>To: Multiple recipients of list <vanagon@lenti.med.umn.edu>
>Subject: Warning - delayed mail
>X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
>X-Info: SISNA
>
>---------------------------------------------------------------------
>
>              ***************************************
>              **       This is a warning only      **
>              **    No action is required by you   **
>              ***************************************
>
>Re: Message to felix@mail.sisna.com
>
>Your message  has not  been  delivered  after  1 hours.   Attempts to
>deliver your message will continue for a further  2 hours.  If it has
>still not been delivered,  it will be returned to you.  The first few
>lines of your message are repeated below.
>
>---------------------------------------------------------------------
>Your message follows:
>
>
>>Received: from [205.138.107.34] by mail.sisna.com (NTMail 3.01.03) id ya917746; Tue, 9 Jul 1996 16:19:58 -0600
>>Received: from [205.138.107.34] by mail.sisna.com (NTMail 3.01.03) id ka916302; Tue, 9 Jul 1996 15:46:10 -0600
>>Received: from [205.138.107.34] by mail.sisna.com (NTMail 3.01.03) id ba914239; Tue, 9 Jul 1996 15:08:25 -0600
>>Received: from [205.138.107.34] by mail.sisna.com (NTMail 3.01.03) id ba909377; Tue, 9 Jul 1996 14:19:42 -0600
>>Received: from [205.138.107.34] by mail.sisna.com (NTMail 3.01.03) id pa907883; Tue, 9 Jul 1996 13:56:51 -0600
>>Received: from [205.138.107.34] by mail.sisna.com (NTMail 3.01.03) id da904075; Tue, 9 Jul 1996 13:11:59 -0600
>>Received: from [205.138.107.34] by mail.sisna.com (NTMail 3.01.03) id sa902062; Tue, 9 Jul 1996 12:48:00 -0600
>>Received: from [205.138.107.34] by mail.sisna.com (NTMail 3.01.03) id ja899037; Tue, 9 Jul 1996 12:22:25 -0600
>>Received: from [128.101.131.51] by mail.sisna.com (NTMail 3.01.03) id la894437; Tue, 9 Jul 1996 11:47:13 -0600
>>Return-Path: <vanagon@lenti.med.umn.edu>
>>Received: from halfdan.med.umn.edu by mhub1.tc.umn.edu; Tue, 9 Jul 96 12:38:09 -0500
>>Date: Tue, 9 Jul 1996 12:38:05 -0500
>>Received: from  (localhost) by halfdan; Tue, 9 Jul 1996 12:38:05 -0500
>>Message-Id: <3190F180.475A@4dmg.net>
>>Errors-To: gsker@lenti.med.umn.edu
>>Reply-To: jwakefield@4dmg.net
>>Originator: vanagon@lenti.med.umn.edu
>>Sender: vanagon@lenti.med.umn.edu
>>Precedence: none
>>From: jwakefield@4dmg.net (john wakefield)
>>To: Multiple recipients of list <vanagon@lenti.med.umn.edu>
>>Subject: Re: Fuel gauge sender question ('66)
>>X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
>>X-Mailer: Mozilla 2.02 (Win16; I)
>>X-Info: SISNA
>>
>>A while back, Erik asked about fuel sender units:
>>  "Is there any way of testing it before I reinstall the whole tank?"
>> 
>>  I expect the normal electrical continuity through movement range test 
>>was related to ALL, but a nice trick that should be used when it applies 
>>to high milage vehicle designs, is to flip the wire wound resistance 
>>sensor coil over before the mobil contact paw abrades all the way through 
>>any of the wire wraps. This generic approach applies to hundreds of 
>>vehicle designs and doubles their effective life.  On some, just bending 
>>the contact paw so that it rubs the coil in a different arc will do.  The 
>>idea's the same: Don't let it wear all the way through any single wire 
>>wrap, and it will keep on serving you well.
>>  Hope this helps someone.
>>
>>  John Wakefield
>>
>>
>>.
>.