Subject: No message text if I don't go with "full headers"

From: Adam J Weitzman <[email-masked]>
Date: Thu, 24 Feb 1994 15:32:08 -0500 (EST)

I'm using Pine 3.07 on a SunOS 4.1.2 UNIX box.

Occasionally, I get mail with just headers and no message. I usually
figure, "Oh, this guy sent something out by mistake" or whatever, but one
time I hit the "H" key to see the full headers, and lo and behold, a
message appeared at the bottom out of thin air. A look at the headers
revealed this: 

Content-Type: MULTIPART/MIXED; BOUNDARY="Boundary (ID mMUBo+QQrtWQIXsCyCqPSw)"

as one of the headers. What is happening here? When I don't have "full
headers" on, it looks like the message is completely blank, and when I
turn the headers on, it looks like a normal mail (with lots of headers).

                                        - Adam J Weitzman
                                          INDIVIDUAL, Inc.
                                          [email-masked]

---

From: David L Miller <[email-masked]>
Date: Thu, 24 Feb 1994 13:13:25 -0800 (PST)

Adam,

It looks like Pine is seeing a MIME message, but is not able to correctly 
parse it as such.  This is often caused by not having the required blank 
line between the header and body of the message.  Or, the boundaries 
between parts may not be in quite the expected form, etc.

My first recommendation would be to upgrade to Pine 3.89.  If Pine 3.89 
still cannot read the problem messages, send us a copy of one of them as 
an attachment and we will figure out what the problem is.

Thanks for the report!

--DLM

|\ |  |\/|  David L. Miller    [email-masked]  (206) 685-6240
|/ |_ |  |  Software Engineer, Pine Development Team   (206) 685-4045 (FAX)
University of Washington, Networks & Distributed Computing
4545 15th Ave NE, Seattle WA 98105, USA

---

From: Mark Crispin <[email-masked]>
Date: Thu, 24 Feb 1994 13:12:57 -0800 (PST)

Hello.  Please save a message which demonstrates this problem to a file, and
then mail that file to us ([email-masked]) as a Pine attachment.
We'll analyze it figure out if it's a bug in our stuff, or if the message is
badly-formed MIME.  If the former, we'll fix the bug; if the latter, we'll get
in touch with the sender so he can fix his bug.