From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] RMail chokes on broken headers
Date: Thu, 15 Oct 2009 06:11:36 -0700 [thread overview]
Message-ID: <1255612194-sup-3880@masanjin.net> (raw)
In-Reply-To: <20091012232215.GD31940@tilus.net>
Reformatted excerpts from Tero Tilus's message of 2009-10-12:
> RMail looks abandoned. Development is pretty much stalled. No
> functional changes since 2004-04-27. None of the reported bugs have
> been fixed. Might it be worth to think about switching to another
> mail lib? TMail author's http://github.com/mikel/mail/ looks
> promising.
Yeah, this is certainly an option. But it seems like a lot of work. And
every day our set of rmail workarounds grows more robust. :)
Not to say I wouldn't accept a patch that magically did this all for me,
of course.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-10-15 13:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 23:22 Tero Tilus
2009-10-15 13:11 ` William Morgan [this message]
2009-10-29 23:02 ` Mariano Mara
2009-10-30 21:50 ` William Morgan
2009-10-31 20:18 ` Mariano Mara
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=1255612194-sup-3880@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-talk@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