Handle unknown message types in the generic content handler rather

than in the RFC822 handler; this will cause them to be displayed using
an output marker rather than throw an error.

diff --git a/uip/mhshowsbr.c b/uip/mhshowsbr.c
index 36b414050755ff03595cbce20e84aa7212c7c598..1f3b6f16a59dda3d591c0b514093e1e7c8e9e57a 100644 (file)
--- a/uip/mhshowsbr.c
+++ b/uip/mhshowsbr.c
@@ -258,8 +258,15 @@ show_switch (CT ct, int alternate, int concatsw, int textonly, int inlineonly,
                                          inlineonly, fmt);
 
                case MESSAGE_RFC822:
                                          inlineonly, fmt);
 
                case MESSAGE_RFC822:

-               default:

                    return show_message_rfc822 (ct, alternate, fmt);
                    return show_message_rfc822 (ct, alternate, fmt);

+
+               /*
+                * Treat unknown message types as equivalent to
+                * application/octet-stream for now
+                */
+               default:
+                   return show_content (ct, alternate, textonly,
+                                        inlineonly, fmt);

            }
 
        case CT_TEXT:
            }
 
        case CT_TEXT: