Re: Any chance of getting gnus to handle mime attachments?

[Stefan Monnier]

> X-From-Line: imap Wed Jun  8 07:39:46 2005
> Return-Path: <support@unidata.ucar.edu>
> Received: from laraine.unidata.ucar.edu (laraine.unidata.ucar.edu 
> [128.117.140.62])
>       by unidata.ucar.edu (UCAR/Unidata) with SMTP id j58Cw7Zu021468
>       for <ed>; Wed, 8 Jun 2005 06:58:07 -0600 (MDT)
> X-Gnus-Mail-Source: imap:mail:INBOX
> Message-Id: <200506081258.j58Cw7Zu021468@unidata.ucar.edu>
> Organization: UCAR/Unidata
> Keywords: 200506081258.j58Cw7Zu021468
> To: ed@unidata.ucar.edu
> Subject: 20050608: netCDF under cygwin
> Reply-to: xxxxx@mail.iap.ac.cn
> Date: Wed, 08 Jun 2005 06:58:07 -0600
> From: Unidata Support <support@unidata.ucar.edu>
> Xref: rodney.unidata.ucar.edu support:178
> Mime-Version: 1.0
> Content-Type: multipart/mixed; boundary="----- Forwarded Message"
> Lines: 3833

It's not clear from the above header what software was used to generate this
email message.  Why don't you ask the sender what software he used and tell
him his software has a bug that makes his forwarded email appear
like garbage.

The kind of brokenness above is not that common, so it's unlikely that you
need to tell *all* the people who send you support email to reform
their mailer.  Or maybe you can just tell them to avoid "forward" and use
some other means.

This said, I do find Gnus's MIME support could be improved w.r.t handling
bad MIME.  E.g. being able to display just the header (and/or the raw
undecoded data) of a particular part of a multipart message; or being able
to tell Gnus to "try and guess"; ...


        Stefan