Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Stern <stern+gnus@cray.com>
Subject: MIME standard for digests not recognized
Date: Fri, 28 Mar 2003 10:22:52 -0800	[thread overview]
Message-ID: <ycc3cl71hc3.fsf@orff.wc.cray.com> (raw)

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




             reply	other threads:[~2003-03-28 18:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-28 18:22 Ted Stern [this message]
2003-03-30  2:34 ` Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ycc3cl71hc3.fsf@orff.wc.cray.com \
    --to=stern+gnus@cray.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).