MIME standard for digests not recognized

MIME standard for digests not recognized

[Ted Stern]

Hi all,

The following MIME header seems like it should be straightforward enough for
Gnus' digest mode to interpret:

,----[ MIME specification ]
| Content-Type: multipart/digest; boundary="++----+-----+-++--------+-+-+----++-----+--+---++---------+--+++----++"
`----

But the gnus-summary "\C-d" digest mode is not able to handle this, mainly
because all of the recognized nndoc-type-alist formats have hardcoded boundary
specifications, and the list server uses a different combination of "+" and
"-" for each digest it sends me.  Each part of the message is recognized as
message/rfc822 format by Gnus, however.

I've commented about this before and it was recommended that I create a new
type in nndoc-type-alist, but 
     1) this seems like overkill when there appears to be a semi-standard MIME
        spec. 
     2) I am not an elisp programmer and couldn't figure out how to do this in
        a million years.

Ted
--
 Ted Stern                           Engineering Applications
 Cray Inc.                               office: 206-701-2182
 411 First Avenue South, Suite 600         cell: 206-383-1049
 Seattle, WA 98104-2860                     FAX: 206-701-2500
 Debuggers' motto:  Frango ut patefaciam -- I break in order to reveal

Re: MIME standard for digests not recognized

[Lars Magne Ingebrigtsen]

Ted Stern <stern+gnus@cray.com> writes:

> The following MIME header seems like it should be straightforward enough for
> Gnus' digest mode to interpret:

[...]

> But the gnus-summary "\C-d" digest mode is not able to handle this,
> mainly because all of the recognized nndoc-type-alist formats have
> hardcoded boundary specifications,

Not mime-parts.  I think the problem is just that it guessed wrong
what the type is.  I've now moved mime-parts earlier in the chain.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen