Re: try to toggle this one. Go ahead, I dare ya.

[Jack Vinson <jvinson@chevax.ecs.umass.edu>]

Shouldn't we be able to uudecode that thing right in gnus?  When I do 
'X v u', I get "wrong type file" and nothing seems to happen.

Anyway, when I save the file and decode the file and then examine it in an
nndoc group the display of the *Summary* buffer looks like the enclosed.
It is a bit messy, but I can see all the parts by "nexting" through the
summary buffer.  

R  [ 154:  Jonas Olsson       ] <* mixed> [Fwd: Returned mail: Service unavailable]
R      [   3:  Jonas Olsson       ] <1 text>
R      [ 138:  Jonas Olsson       ] <2 rfc822>
R          [ 115:  Mail Delivery Subsy] <2.* report> Returned mail: Service unavailable
R              [   9:  Mail Delivery Subsy] <2.1 text>
R              [   9:  Mail Delivery Subsy] <2.2 delivery-status>
R              [  80:  Mail Delivery Subsy] <2.3 rfc822>
R                  [  53:  Jonas Olsson       ] <2.3.* mixed> [Fwd: 2 byte integer generates Too big PDU]
R                      [   1:  Jonas Olsson       ] <2.3.1 text>
R                      [  39:  Jonas Olsson       ] <2.3.2 rfc822>
R                          [  28:  Jonas Olsson       ] <2.3.2 text> 2 byte integer generates Too big PDU

However, when I view any part but the original (by pressing the button), I
am dropped into an *mm* buffer which is in fundamental-mode and I cannot
tab to the next button.  The button itself is active and it takes me to the
next part.  When I get to the message parts this way, I get the following
train:

* The article with one button: [2. message/rfc822].
* The message from the daemon with its headers and a button:
  [3. message/rfc822]. 
* A forwarded message (Subject: [Fwd: 2 byte integer generates Too big PDU])
  with a button: [2. message/rfc822]. 
* Finally, the message itself (Subject: 2 byte integer generates Too big PDU).


-- 
Jack Vinson <jvinson@chevax.ecs.umass.edu>    http://www.cis.upenn.edu/~vinson/
Zippy: ...Um...Um...