🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: gnu.emacs.vm.bug
Article #644

Re: message/digest format

#644
From: Kevin Rodgers
Date: Wed, 25 Aug 2004 15:36
45 lines
2874 bytes
Douglas Gray Stephens wrote:
 > I'm subscribed to the ActiveState perl-win32-users bulletin board
 >  http://listserv.ActiveState.com/mailman/listinfo/perl-win32-users
 > and I think that they changed the MIME format earlier this year, so that
 > the
 >  multipart/digest
 > now has a
 >  message/rfc822
 > MIME header before each message.  This is causing VM not to show the
 > correct summary for the digest, and each message in the digest is
 > treated as having a message/digest attachment, which must be opened.
 >
 > Looking at the RFCs (
 >  http://www.ietf.org/rfc/rfc2046.txt
 > ), it appears that this MIME format may be valid:
 >   If no Content-Type field is present it is assumed to be
 >   "message/rfc822" in a "multipart/digest" and "text/plain"
 >   otherwise.

I thought the presence of the blank line between the boundary and the
individual message headers might be a problem, since the first 2
paragraphs of section 5.1 of the RFC say that a blank line separates
the boundary from the body -- which would mean the headers were part
of the entity and not information for the MIME processor about the
entity.  But I sent myself a test multipart/digest with VM, and it
also puts a blank line between each boundary and the following message
headers.

That digest displayed fine, so I edited it to change the individual
Content-Type headers from text/plain to message/rfc822.  Here's where
it gets interesting: some messages still displayed as before, but some
displayed as you describe.  When I looked closer, the messages that
displayed normally also had "Content-Disposition: inline" headers.  I
usually have vm-honor-mime-content-disposition set to t, but when I
set it to nil it caused all the messages to be displayed abnormally.

 > Is there a switch in VM to enable it to support this type of MIME
 > message?

No, something needs to be tweaked in the code so that the messages
burst from a multipart/digest into a folder for display are handled
the same regardless of the individual Content-Type headers.

-- 
Kevin Rodgers
Technical Details
Message-ID: <412CB1E5.1030808@yahoo.com>
Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!fu-berlin.de!uni-berlin.de!not-for-mail
References: <bb445011.0408241438.245fb5a3@posting.google.com>

Show Full Headers
Complete Article Headers
X-Google-Thread: f6829,df85dad5d530ee2c
X-Google-Attributes: gidf6829,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!fu-berlin.de!uni-berlin.de!not-for-mail
From: Kevin Rodgers <ihs_4664@yahoo.com>
Newsgroups: gnu.emacs.vm.bug
Subject: Re: message/digest format
Date: Wed, 25 Aug 2004 09:36:05 -0600
Lines: 46
Message-ID: <412CB1E5.1030808@yahoo.com>
References: <bb445011.0408241438.245fb5a3@posting.google.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: news.uni-berlin.de yPuULjV8gt/uOm2R7wLtUQITasJDHY0kkSGGBDDcd/0eRjp6g=
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:0.9.4.1) Gecko/20020406 Netscape6/6.2.2
X-Accept-Language: en-us