From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.117.16 with SMTP id p16cs319521agc; Fri, 30 Oct 2009 14:59:56 -0700 (PDT) Received: by 10.224.36.161 with SMTP id t33mr1283410qad.346.1256939995770; Fri, 30 Oct 2009 14:59:55 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 35si5027096qyk.96.2009.10.30.14.59.55; Fri, 30 Oct 2009 14:59:55 -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 7E9D4158806E; Fri, 30 Oct 2009 17:59:55 -0400 (EDT) Received: from entry.masanjin.net (masanjin.net [209.20.72.13]) by rubyforge.org (Postfix) with ESMTP id 01E491858289 for ; Fri, 30 Oct 2009 17:50:41 -0400 (EDT) Received: from w by entry.masanjin.net with local (Exim 4.69) (envelope-from ) id 1N3zMn-0006pH-Ql for sup-talk@rubyforge.org; Fri, 30 Oct 2009 14:50:41 -0700 From: William Morgan To: sup-talk In-reply-to: References: <20091012232215.GD31940@tilus.net> <1255612194-sup-3880@masanjin.net> Date: Fri, 30 Oct 2009 14:50:41 -0700 Message-Id: <1256939410-sup-8456@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 Mariano Mara's message of 2009-10-29: > Hi there, I'm facing the same error as reported by Tero. I applied the > modifications he sent, however it's failing in another place and my > total ignorance of Ruby prevents me from fixing it. Would anyone be so > kind to suggest a workaround? This is fixed in git master. Maybe I should release an 0.9.1. -- William _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk