From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] sup failing to display the text of a message
Date: Tue, 10 Jul 2007 08:45:38 -0700 [thread overview]
Message-ID: <1184081531-sup-3358@south> (raw)
In-Reply-To: <1183992180-sup-9883@mona>
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 <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2007-07-10 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 1:30 jeff covey
2007-07-07 12:17 ` jeff covey
2007-07-08 15:44 ` William Morgan
2007-07-09 14:44 ` jeff covey
2007-07-10 15:45 ` William Morgan [this message]
2007-07-10 17:40 ` jeff covey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1184081531-sup-3358@south \
--to=wmorgan-sup@masanjin.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox