[sup-talk] Case-sensitivity of Content-Type: more RubyMail stupidity?
kevinr at free-dissociation.com
Sat Sep 12 15:10:03 EDT 2009
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
So the above should be handled just like the many mails with headers of
> 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 Riggle (kevinr at free-dissociation.com)
More information about the sup-talk