info-gnus-english
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Ed Hartnett
Subject: Re: Any chance of getting gnus to handle mime attachments?
Date: Wed, 08 Jun 2005 10:11:17 -0600
User-agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.4 (gnu/linux)

Karl Kleinpaste <karl@charcoal.com> writes:

> If there are proper header indications, namely MIME-Version and
> Content-Type, Gnus will handle it fine.  Lacking those, Gnus correctly
> assumes text/plain.
>
> Are there such proper headers?  If so, then there is a deeper
> problem.

Here's the headers. Seems like there is a Mime-Version and a
Content-Type.

Any help would be appreciated.

Thanks,

Ed

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

>To: support@unidata.ucar.edu
>From: =?gb2312?B?zfXUvQ==?= <xxxxx@mail.iap.ac.cn>
>Subject: =?gb2312?B?UmVwb3J0IG5ldGNkZiBJbnN0YWxsIHByb2JsZW0=?=
>Organization: ?
>Keywords: 200506081058.j58AwQZu008755 netCDF cygwin

This is a multi-part message in MIME format.

------=_NextPart_RTV6YGPT0A6RG9PMMD0TK2F2
Content-Type: multipart/alternative;
        boundary="----=_NextPart_VVQY6VL4U8EJT0IS0DPWS595"


------=_NextPart_VVQY6VL4U8EJT0IS0DPWS595
Content-Type: text/plain;
        charset="gb2312"
Content-Transfer-Encoding: base64

RGVhcnMsDQpJIHdhbm5hIGluc3RhbGwgdGhlIG5ldGNkZiBvbiBteSBDeWd3aW4gc3lzdGVtICgg
bXkgT1MgaXMgd2luZG93czIwMDApLCBidXQgY2Fubm90IG1ha2UgaXQuIEkgaGF2ZSB0aWVkIHRo
ZSB0cm91Ymxlc2hvb3Rpbmcgc3VjaCBjb3B5IGJpbmFyeSBjb2RlIG9mIGxpbnV4XzIuNC1pNjg2
IHRvIC91c3IvbG9jYXIsIGJ1dCBpdCBzdGlsbCBjYW5ub3Qgd29yay4gRm9sbG93aW5nIGlzIHRo
ZSBpbmZvbWF0aW9uIGFib3V0IHRoZSBpbnN0YWxsYXRpb24sIHBscyBraW5kbHkgaGVscCBtZS5U


-- 
Ed Hartnett  -- ed@unidata.ucar.edu


reply via email to

[Prev in Thread] Current Thread [Next in Thread]