Subject: header size inconsistant (sic)

From: Dave Horsfall <[email-masked]>
Date: Sat, 2 Sep 2000 20:06:14 +1000 (EST)

First, it's "inconsistent," not "inconsistant."

Anyway, this has to be the most useless error message ever.  All of a
sudden, PINE (4.21, self-compiled on Solaris 2.6) is core-dumping with
this message as its last gasp.

Now where, exactly, is the problem in my mailbox?

-- 
Dave Horsfall CL VK2KFU  [email-masked]  Ph: +61 2 9978-7493  Fx: * 9978-7422
Geac Computers P/L (FGH Division) 2/57 Christie St, St Leonards 2065, Australia

-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Bruce Cohen <[email-masked]>
Date: Sat, 2 Sep 2000 12:38:32 +0200 (MET DST)

Could the developers please come into this discussion? Too many of us are
having problems that are definitely header-related and as far as I can
tell they don't seem to have been solved in 4.21, considering the frequent
complaints in the Pine Discussion Forum. I for one am certainly wary of
upgrading from 3.96 (which used to work PERFECTLY) in view of what I have
been reading here. Exactly what is going on?

(a msg from me and one from Atle Weibell follow the one from Dave, but
there have been many others the past few weeks). 

Bruce Cohen

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

>Now where, exactly, is the problem in my mailbox?

-- >Dave Horsfall CL VK2KFU [email-masked] Ph: +61 2 9978-7493 Fx: *9978-7422
-- >Geac Computers P/L (FGH Division) 2/57 Christie St, St Leonards 2065, 
-- >Australia

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

Date: Sat, 12 Aug 2000 08:12:26 +0200 (MET DST)
From: Bruce Cohen <[email-masked]>
To: Pine Discussion Forum <[email-masked]>
Cc: Atle Weibell <[email-masked]>
Subject: Re: Message to save shrank

I, too, have been having problems with message to save shrank for some months.
The problem started when my provider installed a different io handler.
If I look at the headers, I see that this new io handler adds a line to 
the first "Received:" header: for example,

    (envelope-from [email-masked])

If I log on to pine and do not open the INBOX and then
quit the automatic move to mbox works fine, however neither the automatic move
or the manual save to mbox will work if the INBOX has actually been opened.

The message will shrink by a certain number of bytes, depending upon who sent
the message. In the above example (PINE-INFO as sender) the message to save
shrinks by 64 bytes - the above line is however only about 48 bytes.

If I look at the headers in the pine INBOX I see that the previous line appears to be
too long (DST is in the wrong place):

Received: from put.worldonline.nl (relay-2.worldonline.nl [195.241.48.138])
        by pop3-1.worldonline.nl (8.9.3 (WOL 1.2)/8.9.3) with ESMTP id UAA22295
        for <[email-masked]>; Wed, 2 Aug 2000 20:54:54 +0200 (MET 
DST)
        (envelope-from [email-masked])

If I then count immediately after MET and count all spaces it's 64 bytes.

If I look at the saved header from the mbox (assuming I can somehow convince
the message to move there), I see that the previous line seems to be OK, if
indeed a trifle long for comfort (76 bytes plus $0A $09). Can it be that
pine expands the TAB to spaces and then recompresses? It it getting confused
because the expanded line is now over 80 bytes? Will this problem disappear
magically if I have the provider upgrade to 4.21 Unix (presently 3.96)?

If I try to respond to a message, the quoting no longer works the way 
it's supposed to: the > only appears on the first line - I have to
add the rest manually!

There are other problems with the INBOX as well, that may or may not be
related to the message shrank problem, but certainly are related to the
change in io handler: 

1) some messages appear twice in the Index - if you read one and quit, the
"duplicate" is gone on the next login. 

2) sometimes messages that aren't marked for deletion are expunged with 
those that are marked. However, on the next login they're (usually) back again
where they belong.

3) sometimes (rarely) messages that are marked for deletion won't expunge.

4) Sorting by date in the INBOX no longer works correctly, as well -
it's ALMOST right, but a few messages will appear out of order...
	
Once a message has made it to the mbox, there are no further problems with
it - it can be moved at will to another folder or whatever.

Can anyone shed any light on the subject?

Bruce Cohen

On Wed, 9 Aug 2000, Atle Weibell wrote:

> Honored Pine users,

>I get this message each time I try to save a mail with attachments to a
>local folder:

>[Message to save shrank!  (#6: 49523 --> 838)

>...where #6 is the message no in INBOX, 49253 the size of the message
>with
>attachment, and 838 the size without attachment.

>I also sometimes get another message:
>[Message size does not match expected size, continuing...]

>This happens also on messages that doesn't contain attachments...

>Anyone knows why this happens?

>Regards,
>-- 
>Atle Weibell | [email-masked] | pr 51690007 | mo 90690010 | fx 51690431

---

From: Eduardo Chappa <[email-masked]>
Date: Sun, 3 Sep 2000 12:55:38 -0700 (PDT)

*** Dave Horsfall ([email-masked]) wrote in the pine-info list about
"header size inconsistant (sic)" on Sep 2, 2000:

:) First, it's "inconsistent," not "inconsistant."
:) 

  That's the message given by 4.21, which comes from unix.c in the
c-client library, its spelling is corrected in the new version of the
library distributed with the next version of pine. If you want to see an
explanation, there was a thread with the same subject as this one (except
by the word sic) in comp.mail.pine, and there you can find what Mark
explained about it.

  (yes, I did look hard enough, just in case this thread comes back again)

-- 
Eduardo
http://www.math.washington.edu/~chappa/pine/

---

From: Bruce Cohen <[email-masked]>
Date: Sun, 3 Sep 2000 23:23:17 +0200 (MET DST)

I don't think that the spelling is the point - it's the header problems
that really concern everyone!