Feature request: decoding gnatsweb attachments

Feature request: decoding gnatsweb attachments

[Alexandre Oliva]

[-- Attachment #1: Type: text/plain, Size: 252 bytes --]

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:


[-- Attachment #2: Type: text/plain, Size: 597 bytes --]

----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=


[-- Attachment #3: Type: text/plain, Size: 351 bytes --]

Note that there are no MIME headers in the enclosing message.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

Re: Feature request: decoding gnatsweb attachments

[ShengHuo ZHU]

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

Re: Feature request: decoding gnatsweb attachments

[Alexandre Oliva]

On Nov  4, 2000, ShengHuo ZHU <zsh@cs.rochester.edu> wrote:

> I never received anything like this.  Where does it come from?

A bug tracking system called Gnats.  It's Free Software (of course),
and widely used in projects such as GCC, glibc, GDB, GCJ, autoconf,
automake, libtool, and the list goes on :-)

> Is the attachment always at the end of the message?

I've never seen anything after it.

> Or Is there something marking the end of the attachment?

A blank line after the base64 encoded stream looks like a good bet.

I may send you a complete message, if you'd like to look into it.

For an example of Gnatsweb in action, see
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?database=gcc&user=guest&password=guest&cmd=login

The bug report containing the attachment I posted is bug #734.

Whenever someone posts a GCC bug report, it's forwarded to gcc-prs and
gcc-bugs@gcc.gnu.org, and attachments are encoded as in the snippet I
posted.  The bug report in question, that I chose just because its
attachment was very small, is archived at
http://gcc.gnu.org/ml/gcc-prs/2000-q4/msg00213.html

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

Re: Feature request: decoding gnatsweb attachments

[Raja R Harinath]

Alexandre Oliva <oliva@lsd.ic.unicamp.br> writes:
> On Nov  4, 2000, ShengHuo ZHU <zsh@cs.rochester.edu> wrote:
> > I never received anything like this.  Where does it come from?
> 
> A bug tracking system called Gnats.  It's Free Software (of course),
[snip]

Then you should be able to fix it to send MIME attachments instead ;-)
Isn't that a more generally useful fix rather than looking for a
gnus-specific solution?

- Hari
-- 
Raja R Harinath ------------------------------ harinath@cs.umn.edu
"When all else fails, read the instructions."      -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing."   -- Roy L Ash

Re: Feature request: decoding gnatsweb attachments

[ShengHuo ZHU]

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:

Added. 

BTW, verifying PGP clear sign is also added. 

ShengHuo

Re: Feature request: decoding gnatsweb attachments

[Alexandre Oliva]

On Nov  4, 2000, Raja R Harinath <harinath@cs.umn.edu> wrote:

> Alexandre Oliva <oliva@lsd.ic.unicamp.br> writes:
>> On Nov  4, 2000, ShengHuo ZHU <zsh@cs.rochester.edu> wrote:
>> > I never received anything like this.  Where does it come from?
>> 
>> A bug tracking system called Gnats.  It's Free Software (of course),
> [snip]

> Then you should be able to fix it to send MIME attachments instead ;-)

Good point :-)

> Isn't that a more generally useful fix rather than looking for a
> gnus-specific solution?

Except that I'd have to ask the maintainers of Gnats in all projects I
run to install the patch.  And I know some of them aren't exactly fans
of MIME :-)

Besides, this wouldn't help me deal with the hundreds of messages I
keep in local folders for fast access :-)


I just thought it would be easier to do in Gnus, since it's already
got all the magic needed to cope with base64 encoding, and already has
special-cases for uuencoded parts.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me