From: kevinr@free-dissociation.com (Kevin Riggle)
Subject: [sup-talk] Case-sensitivity of Content-Type: more RubyMail stupidity?
Date: Sat, 12 Sep 2009 15:10:03 -0400 [thread overview]
Message-ID: <1252781841-sup-6303@black-opal.mit.edu> (raw)
Several people from whom I receive e-mail regularly use a MUA which
generates Content-Type: headers of the form
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
The symptoms I see are that I don't get any preview text, and Sup shows
the message as consisting only of a spurious attachment of the form:
> - Attachment: sup-attachment-1252774311-2202. (8 lines)
(Note no file-type suffix.)
RFC 2045 (the MIME specification) section 5.1 says in part
> The type, subtype, and parameter names are not case sensitive. For
> example, TEXT, Text, and TeXt are all equivalent top-level media
> types.
So the above should be handled just like the many mails with headers of
the form
> Content-Type: text/plain; charset="us-ascii"; format=flowed
I get, which Sup handles perfectly.
I theorize that RubyMail is being case-sensitive where it shouldn't.
Given the number of work-arounds Sup has had to implement to compensate
for RubyMail's stupidity, and that RubyMail is currently unmaintained,
has any thought been given to switching Sup to eg. TMail
(http://tmail.rubyforge.org), which is maintained?
Failing that, thoughts on how best to work around this problem in Sup?
- Kevin
--
Kevin Riggle (kevinr at free-dissociation.com)
http://free-dissociation.com
next reply other threads:[~2009-09-12 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 19:10 Kevin Riggle [this message]
2009-09-26 18:17 ` William Morgan
2009-09-26 21:35 ` Kevin Riggle
2009-09-27 1:46 ` William Morgan
2009-09-27 7:10 ` Kevin Riggle
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=1252781841-sup-6303@black-opal.mit.edu \
--to=kevinr@free-dissociation.com \
/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