Subject: Re: message shrank

From: Joe Brennan <[email-masked]>
Date: Thu, 31 Aug 95 11:43:26 EDT

> 	[Message to save shrank! (#msgno: n_bytes --> n1_bytes)]
> 
> And nothing is saved.
> 
> Fingles law applies. It doesn't happen every time, only when its really
> important.
> Any ideas/fixes?

When we see it (rarely), the message has control-M characters in it.
Now that I noticed this, I've verified it every time, maybe 5 times.
The messages originate on PCs and get inserted with both control-J and
control-M at end of line, non-unix-style.

Try replacing the control-M's with something else by editing mbox.
Careful, if you use mtext format, to do a one-for-one replacement of
the characters; sed might be good.  For mbox format, just delete them.

Comments from the pine team would be welcome of course.

Joseph Brennan     Academic Information Systems
                   Columbia University in the City of New York
                   [email-masked]

---

From: Mark Crispin <[email-masked]>
Date: Thu, 31 Aug 1995 20:21:43 -0700

Yes, this is a known bug that will be fixed in Pine 3.92.  If you
substitute the imap-3.5 toolkit with the imap-3.6.BETA toolkit and rebuild
Pine and imapd you'll get the fix; otherwise just wait until Pine 3.92
comes out.

The bug is that the calculation of the "RFC 822 size" (the size of the
message in RFC 822 format using CR LF newlines) was a guesstimate (Unix
size + # of newlines) in the older version, and the calculation didn't do
the right thing with CR LF newlines.  The newer version handles CR LF
newlines that are already in the message, and doesn't count them twice.

The question is; how did those CR's get in the file, since sendmail is
supposed to suppress them.  Was NFS used from the PC?

>                    Columbia University in the City of New York

-- Mark --

DoD #0105, R90/6 pilot, FAX: (206) 685-4045  ICBM: N 47 39'35" W 122 18'39"
Science does not emerge from voting, party politics, or public debate.