Bug 208021 - knode will not start a viewer for a jpeg if the message only contains a jpeg
Summary: knode will not start a viewer for a jpeg if the message only contains a jpeg
Status: RESOLVED FIXED
Alias: None
Product: knode
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-20 21:18 UTC by John K. Herreshoff
Modified: 2009-10-11 00:40 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description John K. Herreshoff 2009-09-20 21:18:42 UTC 
Version:           0.99.01 (using 4.2.4 (KDE 4.2.4), volkerdi@slackware.com)
Compiler:          gcc
OS:                Linux (i686) release 2.6.29.6-smp

knode will not start a viewer for a jpeg if the message only contains a jpeg.  For example, a message that begins with a jpeg such as this:  begin 644 l&m157.jpg
M_]C_X``02D9)1@`!`0```0`!``#_X2+717AI9@``24DJ``@````!`&F'!``!
M````&@```"P````!``"0!P`$````,#(Q,``````%`!H!!0`!````;@```!L!
M!0`!````=@```"@!`P`!`````@````$"!``!````?@````("!``!````42(`
M``````!(`````0```$@````!````_]C_X``02D9)1@`!`0```0`!``#_VP!#

will not open the viewer.  Messages with jpegs will show the jpeg.
Comment 1 John K. Herreshoff 2009-09-20 21:51:47 UTC 
I did a bit more research by looking at the source.  The following does not open a viewer:

Xref: number.nntp.dca.giganews.com alt.binaries.pictures.rail:1015180

Photo by xxxx xxxxxxx, my scanned collection.

begin 644 D&H650atBinghamtonNY1985JaimeSerensitsScanColl.jpg
M_]C_X``02D9)1@`!`0$"6`)8``#_VP!#``,"`@,"`@,#`P,$`P,$!0@%!00$
M!0H'!P8(#`H,#`L*"PL-#A(0#0X1#@L+$!80$1,4%145#`\7&!84&!(4%13_
MVP!#`0,$!`4$!0D%!0D4#0L-%!04%!04%!04%!04%!04%!04%!04%!04%!04

This opens a viewer:

Xref: number.nntp.dca.giganews.com alt.binaries.pictures.rail:1015147

This is a multipart message in MIME format.

--HW.C6DB7E91000021D2B01AD9AF
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Content-Type: image/jpeg; name="DSS&A101_2009-09-11_Duluth_MN_f.jpg"
Content-Transfer-Encoding: Base64
Content-Disposition: attachment; filename="DSS&A101_2009-09-11_Duluth_MN_f.jpg"

/9j/4AAQSkZJRgABAgEASABIAAD/4RmcRXhpZgAASUkqAAgAAAAKAA8BAgAGAAAAhgAAABAB
AgANAAAAjAAAABIBAwABAAAAAQAAABoBBQABAAAAmQAAABsBBQABAAAAoQAAACgBAwABAAAA
AgAAADEBAgAnAAAAqQAAADIBAgAUAAAA0AAAABMCAwABAAAAAgAAAGmHBAABAAAA5AAAAJQD
AABDYW5vbgBDYW5vbiBFT1MgNUQAgPwKABAnAACA/AoAECcAAEFkb2JlIFBob3Rvc2hvcCBF

Knode knows what to do if the content information is present.
Comment 2 Olivier Trichet 2009-10-11 00:40:35 UTC 
Thanks for the report.

The problem has already been fixed. In version newer than KDE 4.3.0, Knode is able to decode "uuencoded" message (those with "begin 644" lines). Thus i'm closing this bug.