From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Case-sensitivity of Content-Type: more RubyMail stupidity?
Date: Sat, 26 Sep 2009 11:17:14 -0700 [thread overview]
Message-ID: <1253988779-sup-2896@masanjin.net> (raw)
In-Reply-To: <1252781841-sup-6303@black-opal.mit.edu>
Reformatted excerpts from Kevin Riggle's message of 2009-09-12:
> I theorize that RubyMail is being case-sensitive where it shouldn't.
Although I love criticizing RubyMail, I think this is Sup's fault. I
don't think it's in RubyMail's proper purview to canonicalize header
values (though header names are fine).
Anyways, I think I've fixed this in git. Give it a try.
> 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?
It's certainly an option, but with so many workarounds invested in
RubyMail, I'm not sure it's a win. A patch that magically makes
everything work would certainly be considered.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-09-26 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 19:10 Kevin Riggle
2009-09-26 18:17 ` William Morgan [this message]
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=1253988779-sup-2896@masanjin.net \
--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