From mboxrd@z Thu Jan 1 00:00:00 1970 From: wmorgan-sup@masanjin.net (William Morgan) Date: Tue, 10 Jul 2007 08:45:38 -0700 Subject: [sup-talk] sup failing to display the text of a message In-Reply-To: <1183992180-sup-9883@mona> References: <20070611013051.GA12580@mona.jeffcovey.net> <1183810570-sup-4651@mona> <1183908397-sup-1704@south> <1183992180-sup-9883@mona> Message-ID: <1184081531-sup-3358@south> Excerpts from jeff.covey's message of Mon Jul 09 07:44:54 -0700 2007: > it still looks the same to me: > > 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. -- William