From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.117.16 with SMTP id p16cs610779agc; Thu, 15 Oct 2009 06:11:50 -0700 (PDT) Received: by 10.224.92.143 with SMTP id r15mr27127qam.105.1255612309851; Thu, 15 Oct 2009 06:11:49 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 35si170297qyk.62.2009.10.15.06.11.49; Thu, 15 Oct 2009 06:11:49 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 5E9B518582D5; Thu, 15 Oct 2009 09:11:49 -0400 (EDT) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 752F318582C1 for ; Thu, 15 Oct 2009 09:11:37 -0400 (EDT) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1MyQ7E-0000cj-IG for sup-talk@rubyforge.org; Thu, 15 Oct 2009 06:11:36 -0700 From: William Morgan To: sup-talk In-reply-to: <20091012232215.GD31940@tilus.net> References: <20091012232215.GD31940@tilus.net> Date: Thu, 15 Oct 2009 06:11:36 -0700 Message-Id: <1255612194-sup-3880@masanjin.net> User-Agent: Sup/git Subject: Re: [sup-talk] RMail chokes on broken headers X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org 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 _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk