From: Tero Tilus <tero@tilus.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Mysterious nil errors
Date: Wed, 10 Mar 2010 08:43:12 +0200 [thread overview]
Message-ID: <1268202637-sup-4495@tilus.net> (raw)
In-Reply-To: <1268196678-sup-9427@ezyang>
Edward Z. Yang, 2010-03-10 06:52:
> I suppose this is something that should be fixed on the rmail
> side...
And this is definitely not the only one. Unfortunately RubyMail
<http://rubyforge.org/projects/rubymail/> is pretty much dead.
It looks like the state of art ruby mail library is currently Mail
<http://github.com/mikel/mail>. I don't know how well it would serve
sup, but rmail definitely has a long list of issues (already worked
around in sup) and switching mail library would be a lot of work.
Thoughts?
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-03-10 6:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 4:50 Edward Z. Yang
2010-03-10 4:52 ` Edward Z. Yang
2010-03-10 6:43 ` Tero Tilus [this message]
2010-03-10 17:24 ` Rich Lane
2010-03-10 17:40 ` Edward Z. Yang
2010-03-10 17:59 ` Rich Lane
2010-03-10 18:06 ` Edward Z. Yang
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=1268202637-sup-4495@tilus.net \
--to=tero@tilus.net \
--cc=sup-devel@rubyforge.org \
/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