Well, I received this from the list, and I could view the cartoon.jpg in the 1990's mail reader of which I spoke.
I was also able to view the attachment by saving the text to a file and using "base64 -d" etc. Here is a session trying to use s-nail (s-nail v14.9.6) however... (inline text inclusion by indenting three spaces...) & set pipe-image/jpeg=' display -font fixed ' & mimeview [-- Message 301 -- 4237 lines, 322396 bytes --]: From [email protected] Wed Jun 17 16:22:59 2020 X-Spam-Status: No, score=-5.2 required=4.0 tests=BAYES_00,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,SPF_HELO_NONE autolearn=ham autolearn_force=no version=3.4.2 Delivered-To: [email protected] From: [email protected] To: [email protected] Date: Wed, 17 Jun 2020 15:20:46 -0400 (EDT) Subject: [S-mailx] Can you view the attachment to this message? X-Virus-Status: Clean [-- No MIME handler installed, or not applicable --] [-- #1.2 4130/317709 image/jpeg, base64, us-ascii --] [-- cartoon.jpg --] Run MIME handler for this part? [no]/yes? yes display-im6.q16: Corrupt JPEG data: 1185 extraneous bytes before marker 0x03 `/tmp/magick-7219o0A-RaVoYzMa' @ warning/jpeg.c/JPEGWarningHandler/352. display-im6.q16: Unsupported marker type 0x03 `/tmp/magick-7219o0A-RaVoYzMa' @ error/jpeg.c/JPEGErrorHandler/322. & The mention of "0x03" is consistent with other errors I saw while experimenting. With the real problem probably being some missing "015" characters being (not) sent to the "display" program. Adrian Pepper [email protected] > From [email protected] Wed Jun 17 16:22:59 2020 > X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on > mx-106.cs.uwaterloo.ca > User-Agent: s-nail v14.9.6 > MIME-Version: 1.0 > Content-Type: multipart/mixed; > boundary="=-=hRSUId_5lpXY4YbfhykAxc_SPHi32_s087NN=-=" > Message-Id: <[email protected]> > Subject: [S-mailx] Can you view the attachment to this message? > > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-ID: <20200617184514.qw-i7%[email protected]> > > > I had a somewhat complex report prepared. > But it boils down to asking list recipients > if and how they can use "s-nail" to usefully > view the attachment to this message. > (Assuming the listserv passes it on > appropriately). > > My diagnosis (using something like) > "set pipe-image/jpeg=' cat - > /tmp/o.$$ '" > is that the input sent to the command used > by "mimeview" is missing all carriage-return > characters (octal 015). Sort of annoying > because if it could be sent the base64 > encoding, it could be made to work. > (Although yes, that would be bundling > the encoding back into the file format). > > I observed the problem under both > Ubuntu 18.04 (s-nail v14.9.6) > Ubuntu 20.04 (s-nail v14.9.15) > > Is the actual "s-mailx" package being distributed anywhere yet? > > FWIW, the mime viewing "just works" when I > email the message to another lxc container > which runs inn2 and saves the message as a > news article which I view using "trn". > (I.e. the version of "trn" does the > decoding and display correctly). > > The cartoon also displays properly > (in non-list test runs) using a basically > 1990's version of "mail" spliced with a > frozen version of "metamail", etc. > > > Adrian Pepper > [email protected] > Content-Type: image/jpeg > Content-Transfer-Encoding: base64 > Content-Disposition: attachment; filename="cartoon.jpg" > Content-ID: <20200617184514.ednlr%[email protected]> [...]
