GNOME Bugzilla – Bug 101483
inline message parts not displayed
Last modified: 2011-12-03 18:14:49 UTC
Inline message/rfc822 parts in news postings are silently not displayed with no indication to the reader that the reader is not seeing the entire posting. If the entire posting is a single message/rfc822 part, then Pan displays the posting as if it were empty. The posting is correctly fetched and saved in the cache. No errors are output when displaying such postings. However, attempting to save such a posting results in many errors and the saved attachments are zero length. At the very least, Pan should display MIME content of type message as if it were text rather than not displaying it at all. -ccwf
Created attachment 13081 [details] Pan cache of multipart containing an linline message/rfc822 part
*** Bug 108485 has been marked as a duplicate of this bug. ***
fejj: I tried viewing the message above in Pan, and text.c::set_text_from_message_nolock()'s call to g_mime_message_foreach_part() seems to only call the foreach func twice, for the text/plain parts wrapping the message/rfc822 part. Is this a parsing bug in GMime?
possibly... I have fixed a parser bug that may have caused such a problem in the latest 2.0.x release. (branch gmime-2-0) just so you realise, the callback should only be called on the message/rfc822 and not on any subparts. Not sure if your code knows to handle that situation? anyways, I suggest syncing up with gmime-2-0. if there are still problems, lemme know (although I just tested the parser on that message and it gets the mime structure right - so latest cvs should work)
Okay. Looks like I'll be updating with GMime's message-id code sooner than I'd wanted to. ;)
This isn't important enough to hold up 0.14.0.
*** Bug 118869 has been marked as a duplicate of this bug. ***
Mass-bumping of 0.14.2 features to 0.14.3 to make way for an emergency 0.14.2 release.
It seems that multipart messages with a Content-Disposition of "inline" are the problem ones. Ones that have a Content-Disposition of "attachment" display completely. This has only been tested on 2 part yencoded JPEGs. Pan version 0.14.2.91 with gmime-2.1.16.
Just checked: this is still happening in the pre-1.0 betas.
Bumping version number based on Chris' Comment #10