Subject: [sup-talk] sup failing to display the text of a message

From: [email-masked] (jeff covey)
Date: Sun, 10 Jun 2007 21:30:51 -0400

sup's displaying the attached message as though it has no text at all; it
doesn't even show the two sections as attachments that can be viewed.

i think that's enough from me for today!  :)

thanks,

-- 
jeff covey
http://jeffcovey.net/

-------------- next part --------------
An embedded message was scrubbed...
From: The freshmeat daily newsletter <freshmeat-news at lists.freshmeat.net>
Subject: [fm-news] Newsletter for Saturday, June 09th 2007
Date: Sun, 10 Jun 2007 00:10:07 -0700 (PDT)
Size: 40585
Url: http://rubyforge.org/pipermail/sup-talk/attachments/20070610/42b1f8bd/attachment-0001.mht 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 229 bytes
Desc: Digital signature
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20070610/42b1f8bd/attachment-0001.bin

---

From: [email-masked] (jeff covey)
Date: Sat, 07 Jul 2007 08:17:14 -0400

> doesn't even show the two sections as attachments that can be viewed.

with the new mime code, this is now showing as:

x Attachment: sup-attachment-1183810370-1070 (multipart/mixed)

thanks!

-- 

jeff covey

http://jeffcovey.net/

---

From: [email-masked] (William Morgan)
Date: Sun, 08 Jul 2007 08:44:22 -0700

> x Attachment: sup-attachment-1183810370-1070 (multipart/mixed)

Hm, that's still not quite what I want, though. What should happen with
is that multipart thing shouldn't be displayed at all, and instead you
should see two inlined, collapsable, individually-savable attachments.

I've committed a change that should have this behavior. But I couldn't
replicate your version from the original message, which is curious, so
let me know how it looks.

-- 
William <wmorgan-sup at masanjin.net>

---

From: [email-masked] (jeff covey)
Date: Mon, 09 Jul 2007 10:44:54 -0400

Excerpts from William Morgan's message of Sun Jul 08 11:44:22 -0400 2007:

> What should happen with is that multipart thing shouldn't be displayed at
> all, and instead you should see two inlined, collapsable,
> individually-savable attachments.  I've committed a change that should
> have this behavior.

it still looks the same to me:

http://jeffcovey.net/tmp/sup-fm_newsletter.png

thanks,

-- 
jeff covey
http://jeffcovey.net/

---

From: [email-masked] (William Morgan)
Date: Tue, 10 Jul 2007 08:45:38 -0700

> http://jeffcovey.net/tmp/sup-fm_newsletter.png

Ok, I subscribed to fm-news just so I could figure out what was going on
here. The problem is that they don't send a MIME-Version: header in the
top-level message headers, so RubyMail doesn't interpret the email as a
MIME message. Which is correct, strictly speaking, though of course it's
better to follow the adage of "lenient in acceptance and strict in
emission". If you add a MIME-Version header back in, everything works as
it should.

To further confuse the issue, the version that you attached back at the
beginning of June apparently had its headers cleaned up by Mutt. Mutt
clearly has more lenient message parsing than RubyMail does, if it does
something reasonable with this message.

So I could patch RubyMail (which is completely unmaintained, so I'd
essentially have to publish the patch in parallel with Sup) to handle
these messages, which is dubious by the RFCs but probably fine in
practice, or I could just ignore the issue as "someone else's problem".
Since the message content is still viewable in Sup, I'm tempted to leave
things as is.

RubyMail really needs a maintainer.

---

From: [email-masked] (jeff covey)
Date: Tue, 10 Jul 2007 13:40:39 -0400

> Since the message content is still viewable in Sup, I'm tempted to leave

ok, thanks for checking into it!

-- 
jeff covey
http://jeffcovey.net/