Gnus development mailing list
 help / color / mirror / Atom feed
From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Feature request: decoding gnatsweb attachments
Date: 04 Nov 2000 15:12:34 -0500	[thread overview]
Message-ID: <2npukba43x.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <or8zr06vy2.fsf@guarana.lsd.ic.unicamp.br>

Alexandre Oliva <oliva@lsd.ic.unicamp.br> writes:

> It would be really nice if Gnus would recognize gnatsweb attachments
> and show them as parts, just like it does with uuencoded data.  Does
> anybody feel like implementing this feature?  The attachments usually
> appear at the end of a message, like this:
> 
> ----gnatsweb-attachment----
> Content-Type: application/octet-stream; name="WordIndex.C"
> Content-Transfer-Encoding: base64
> Content-Disposition: attachment; filename="WordIndex.C"
> 
> bmFtZXNwYWNlIExvbmdWaXJ0dWFsTWVtb3J5IHsKCiAgdGVtcGxhdGUgPGNsYXNzIHNpemVfdD4K
> ICBjbGFzcyBMaW5lYXJNZW0KICB7CiAgICBzdHJ1Y3QgQmxvY2tIZWFkCiAgICB7CiAgICAgIHNp
> emVfdCBzaXplOwogICAgfTsKICAgIHR5cGVkZWYgaW50IGlpOwogICAgaWkgUmVhZEJsb2NrSGVh
> ZCgpOwogICAgdmlydHVhbCByZWFkRGV2KCl7fTsKICBwdWJsaWM6CiAgICBMaW5lYXJNZW1fKCl7
> cmVhZERldigpO30KICB9OwoKICBtbW0oKQogIHsKICAgIExpbmVhck1lbTxpbnQ+IGxsOwogICAg
> bGwuTGluZWFyTWVtXygpOwogIH0KfQo=
> 
> Note that there are no MIME headers in the enclosing message.

I never received anything like this.  Where does it come from?  Is the
attachment always at the end of the message?  Or Is there something
marking the end of the attachment?

ShengHuo



  reply	other threads:[~2000-11-04 20:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-04  7:24 Alexandre Oliva
2000-11-04 20:12 ` ShengHuo ZHU [this message]
2000-11-04 21:15   ` Alexandre Oliva
2000-11-04 22:46     ` Raja R Harinath
2000-11-06  3:35       ` Alexandre Oliva
2000-11-05  0:17 ` ShengHuo ZHU

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=2npukba43x.fsf@tiger.jia.vnet \
    --to=zsh@cs.rochester.edu \
    /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).