Subject: pine doesn't like Florida

From: Bob Carlitz {NWNet} <[email-masked]>
Date: Thu, 18 Feb 1993 16:29:49 -0800 (PST)

Messages coming in from firn (the Florida school network) now cause pine to
die a horrible death.  Attached below is a sample.  Put this in a pine
folder, and you can see pine wither.  I have seen similar behavior under
SunOS and Ultrix, both with version 3.05.  The firn headers look a little
odd to me, but I don't see anything obviously wrong with them.  The
Alternate-recipient and Disclose-recipients headers are something new to
me.  I'm not sure if they have been part of the firn headers previously.

Cheers!
Bob Carlitz

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

>From [email-masked] Tue Feb 16 13:02:52 1993
Mr-Received: by mta FIRNVX; Relayed; Tue, 16 Feb 1993 12:54:55 -0500 (EST)
Alternate-Recipient: prohibited
Disclose-Recipients: prohibited
Date: Tue, 16 Feb 1993 17:46:00 EST
From: "Ann S. Johnson 813-361-6472, Ext. 31, ext. 32" <[email-masked]>
Subject: Veil Joze
To: [email-masked]
Posting-Date: Tue, 16 Feb 1993 17:52:00 EST
Importance: normal
Priority: normal
X400-Mts-Identifier: [;55452161203991/141602@FIRNVX]
A1-Format: 
A1-Type: MAIL
Hop-Count: 0
Status: RO

Please send me more information on your project Veli Joze.  We are a middle 
school in Sarasota, Florida, using the modem from the media center.  I am 
wondering what our obligation would be in addition to the pen pal letters?  I 
have 3 students interested in this project.  Would the letters be sent by 
e-mail?  or by surface mail from our end?  Is this an open-ended project?  How 
would replies from Veli Joze be received?  We really would like more 
information.  Thanks,

Ann Johnson
media specialist
Brookside Middle School
3636 S. Shade Ave.
Sarasota, Fla.   34329

---

From: Mark Crispin <[email-masked]>
Date: Thu, 18 Feb 1993 18:33:06 -0800 (PST)

Bob -

     Thank you for your bug report, and for providing sample data that causes
the problem.  This problem is a c-client bug in handling invalid MIME data.

     The cause of the crash is evil data in the headers; the message claims to
be in MIME format (``Mime-Version: 1.0''), and there is a ``Content-Type:''
header line.  However, there is no data for that header.  The parser detected
the error and declined to attempt to parse the Content-Type: information.
Unfortunately, the error case was bundled with the ``not a Content-Type
header, try Content-Transfer-Encoding'' case, and it fell into that code with
invalid context.  The fix was to implement the error case separately.

     A patch to the c-client module rfc822.c is MIME attached to this message.
Please let me know if you need any assistance in installing this patch on your
system.

     If you could, please also ask your correspondent at Florida to inquire as
to what could be causing her mailer to send invalid MIME data to you.  I guess
this is an X.400/MIME gateway that is behind all this, but there is inadequate
information to be sure.

-- Mark --